It seems that Windows Subsystem for Linux (WSL) is getting much more mature than the time when it first came out. Fewer and fewer people keep questioning its fitness for daily development. Tuning WSL to be a neat developing environment and how to SSH into WSL the topic I am going to share with.
The installation entry of several Linux distributions available for WSL has been moved to Microsoft Store since the Fall Creators.
It means you can install a Linux distribution as simple as installing an app from the store. The moment I am writing this, Ubuntu, Debian, OpenSUSE and Kali Linux are officially collected into the WSL family.
I choose Debian as my first trial for WSL.
If nothing goes wrong, the familiar icon will show up in the start menu after the installation. Click it, boot it on and create your Linux user account.
As you can see in the Task Manager, required few seconds to get ready, WSL have very small demand for resource and please don't forget that it is able to offer almost full Linux experience to you. So that is pretty good enough as a subsystem.
By the way, this command can lead you to your C:/.
Similarly, /mnt/d for D:/ and so on.
You can tweak it in the same way as you play with Linux as usual when you have got this far. The following are things I have done just after the installation.
Replacing stable to testing will let your Debian have access to the latest version of software updates.
sudo nano /etc/apt/sources.list
Select your language to add UTF8 locales support by doing this.
sudo dpkg-reconfigure locales
The path to Debian(WSL) root follows the format:
However, do not move or delete or do anything else on files in WSL with Windows File Explorer which might mess up the file permission on Linux File System. That causes tons of problems. Here it can only be used as a single-function graphical File Explorer.
Considering that it is a kind of awkward experience to run bash in CMD, so here I introduce MobaXterm to you. Next, we are about to build up an SSH server on WSL and pair it with MobaXterm through SSH connection.
OpenSSH is the premier connectivity tool for remote login with the SSH protocol.
sudo apt-get install openssh-server
Edit the configuration and change the listening port for the reason that Port 22 as the default setting has been already taken by SSH service running on Windows.
sudo nano /etc/ssh/sshd_config
To make sure SSH server on WSL works well, change Port 22 into Port 2018 or whatever you prefer.
Port 2018 ListenAddress 0.0.0.0 PermitRootLogin prohibit-password
the above is the scanty lines you have to deal with in the sshd_config. Then start the SSH service.
sudo service ssh start
MobaXterm has not only SSH support but also full X-Server support if you need. Two editions (Home Edition and Professional Edition) are provided with free one and paid one.
I download MobaXterm Home Edition (Portable edition) which already fulfils my demand.
Create a new session and edit its configuration. Remote host is set as 127.0.0.1. Remember that Port should be 2018 or the same port you decided several minutes ago. You can tweak other settings catered for your appetite.
If your Debian is running well with SSH enabled, it must work. Select Remember the Password to save the time you type in your password whenever booting the WSL.
Now enjoy WSL with the excellent terminal experience supplied by MobaXterm.
It is so unpleasant to manually start SSH service each time you turn WSL on and the bot to boot WSL at the same time as you log in Windows can be the thing what you want.
Also, you will soon notice that the SSH connection goes bad when you shut down the CMD window which is quite bothering.
Here comes the solution to the three so-called problems.
Write a shell script named init.sh placed in /home.
sudo -S service ssh start << EOF <your_password> EOF
Replace <your_password> to your root password.
The object of the tiny script is to start SSH service in sudo mode when you execute this shell.
Write a VBS script on your Windows host.
Set ws = CreateObject("Wscript.Shell") ws.run "bash /home/init.sh",vbhide
To mention that, WSL can be start up by typing bash in CMD or Powershell. The script is so self-explain that it will obviously run the init.sh as well after booting WSL.
vbhide at the end of the line tells that it runs silently in the background.
Actually, it doesn't matter that what sort of name you give to the shell above and where you place it. Just to be sure the path-to-the-shell has to be identical in two scripts.
It is much easier to achieve this goal since the big steps have got settled in the previous move.
Set the VBS script into the scheduled tasks performing when Windows host logins.
Reboot Windows and keep an eye on the Task Manager. if two processes named init (depends on the name of the shell) and sshd exist, then you can immediately start MobaXterm to SSH into WSL without any other keyboard job.
Now, the complete WSL with SSH workflow has been set up.
Thanks for reading :)