Windows 10 – Installing Linux SubSystem

Background

Availing Linux on MS Windows 10.

Here is the guide that we will be using:

Windows 10 Installation Guide
Install the Windows Subsystem for Linux
Link

Outline

  1. Enable Windows Feature
    • Microsoft Windows Subsystem Linux
  2. Review OS Version
    • Issue SystemInfo and get OS Version and Build Number
  3. Choose Install Location, based on Build Number
    • If Build Number > 16215
      • We can install from Windows Store
    • Else
      • Enable Windows Developer Mode
      • Start Bash or use “lxrun /install
  4. Register Product
  5. Create Linux User
  6. Set root user’s password

 

Install Steps

Enable Windows Optional Features

Microsoft-Windows-Subsystem-Linux

Code

powershell -C "Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux"

System Info

Code


powershell -C "systeminfo | Select-String 'OS' "

Output

version_20180610_0902PM

Explanation

As our Build Number ( 17134 ) is greater than 16215, we can install via “Microsoft Store“.

Microsoft Store

Visit Microsoft Store and search for Linux.

https://www.microsoft.com/en-us/search/result.aspx?q=linux

Here is the result of that search:

MicrosoftStore_Linux.PNG

 

SUSE Linux Enterprise Server 12

We chose to go with SE Linux.

SUSE Linux Enterprise Server 12 – Get

SUSELinuxEnterprise_20180610_0905PM.PNG

Use across your devices

UseAcrossYourDevices_20180610_0906PM.PNG

Add your Microsoft account to Microsoft Store

AddYourMicrosoftAccountToMicrosoftStore_20180610_0921PM [brushedup].PNG

Enter Password

AddYourMicrosoftAccountToMicrosoftStore_EnterPassword_20180610_0923PM.PNG

Installing

Installing_20180610_0911PM

SUSE Linux Enterprise Server 12 – Registration +User

registration_20180610_0926PM.PNG

SUSE Linux Enterprise Server 12 – Registration +User +Password

registrationUserAndPassword_20180610_0927PM.PNG

Validation

Bash

uname

Get Linux Version

Code


uname -r

Output

bash_uname_20180610_0938PM

List Users

Code


cat /etc/passwd

Output

security_users_20180610_0947PM.PNG

References

  1. Microsoft
    • Install the Windows Subsystem for Linux
      • Install the Windows Subsystem for Linux
        Link
    • Rich Turner
      • Bash on Ubuntu on Windows – Download Now!
        Link

Technical: Linux – Remote Desktop from Linux to MS Windows ( Using rdesktop )

Technical: Linux – Remote Desktop from Linux to MS Windows ( Using rdesktop )

Background

I need to be able to remotely connect from my Linux\CentOS box to my MS Windows box.

In this post, we will use rdesktop.

 

On Linux box, Install rdesktop

 

Is rdesktop installed

Is rdesktop installed?


rpm -qa | grep -i "rdesktop"

Output:

IsRemoteDesktopInstalled

In our case, we come back with rdesktop-1.7.1-1.el6.i686.  What does that name in terms of versioning:

 

 

Install rdesktop if not installed

Install rdesktop if not installed


sudo yum -y install rdesktop

Output:

yumInstall

On Linux box, Use rdesktop

 

On Linux box, launch rdesktop

Syntax:

rdesktop <hostname>

 

Sample:

rdesktop hrdb

 

On Linux box, enter user’s logon credentials

remoteDesktopLoginScreen

 

 

 

Acknowledgment

Acknowledging Narad Shrestha @ techmint.com as I followed his blog post
( http://www.tecmint.com/how-to-use-rdesktop-in-redhat-centos-fedora/ ).

And, never once did I get lost.

 

Listening

Listening to …

Aloe Blacc – Wake me up

 

References

Technical: Linux\CentOS – Network – Full Qualified Domain Name on Comcast Home Network \ In-house DNS Server

Technical: Linux\CentOS – Network – Full Qualified Domain Name on Comcast Home Network \ In-house DNS Server

Introduction

I have a little home Network behind my Wireless Access Point.  But, lately one of the boxes that I need to access has being up and down.  And, I really need it to be up.

Quick Analysis

I am bit disinclined to do heavy network troubleshooting. I just need need things up; reliably and running.

What is wrong?

  • Is it a Comcast problem; btw Comcast is my ISP
  • Is it just this old LinkSys Home Router – I have it fronting the internal network; acting as a DHCP host, distributing IPs and forwarding network packets based on Port Forwarding – Traffic Cop, the good one – Looks at Port# and sends it over to specific machines
  • Is it my Linux box (CentOS)
  • It it an on \ off again Software Firewall on the Linux box

Usually, it wouldn’t bother me.  But, I really need to learn.

Comcast Network (thinking….)

I know I am entitled to 5 IPs from Comcast; and I have a spare one.

So for this one host that I need to communicate with, I will like to bypass the LinkSys Router and connect directly to the network switch that is connected to the Cable Modem

Comcast Network (Connected)

Once that connection is made, I have a good world reachable IP Address.  Hopefully, it will stay up and available.

Fully Qualified Domain Name

As the host is a box that will be running Hadoop, I know I need really good and firm FQDN.

What is the Network Domain Info

What is Comcast DHCP giving out?

Checked /etc/resolv.conf and have this entries:

Entry Value
domain hsd1.ca.comcast.net
search hsd1.ca.comcast.net
nameserver 75.75.75.75
nameserver 75.75.76.76

What do we want it to be?

I really do not care much about the details.  But, I need to be able to control my destiny; which means having my own domain data:

Here is what we came up with:

Entry Value
domain labdomain.org
search labdomain.org
nameserver 24.6.75.90 (labdomain.org DNS Server)

DNS Server Changes

Create A and “Reverse Lookup” entries for our linux host.

Our DNS Server happens to be a Windows based, and we will just use a GUI to make the changes.

DNS - A Entry

Linux Node DNS Changes

On the linux node, update /etc/resolv.conf with our updated DNS entries.

# Generated by NetworkManager
domain labDomain.org
search labDomain.org
nameserver 24.6.75.90

Explanation:

  • Our domain name is labDomain.org
  • Our DNS Suffix is labDomain.org
  • In our case, as we getting an IP from Comcast and a home grown network domain, we need to ensure that we choose our own DNS Server (that is also reachable over the Net).

Work Arounds

In case you do not have a good DNS Server or limited network addresses, please consider using a third party Dynamic DNS Provider.

My favorite used to be http://dyn.com/dns/, but it seems that they are pulling back on free FQDNs.

Though, I have yet to try noip.com, I have being hearing good things about it.