WSL now installs as WSL2 by default, but older machines (mostly laptops) may not have the Hyper-V Virtualization hardware and may have to run WSL1.
This is fine: the behaviour is nearly identical so far as an expo laptop is concerned, where you just want to use rsync and scp. An old 2011-era PC has
@@ -40,9 +41,9 @@ certainly have to move all your code to the internal network share e.g. \\w
is how it looks when you are browing from Windows.
(No, don't try to be cute and keep it on /mnt/c/ and just put a soft link in /home/expo/. That doesn't work either.)
This means that the code is actually living on a Linux ext4 filesystem hidden away on your disc where you can only see it using the
-'network' method \\wsl$\Ubuntu-20.04\home\expo\troggle\. This means that file access is somewhat faster too but you probably won't notice. You will need to make sure that your backup/archive methods access this filesystem though.
+'network' method \\wsl$\Ubuntu-20.04\home\expo\troggle\. This means that file access is noticably faster too. You will need to make sure that your backup/archive methods access this filesystem though.
- rsync doesn't work with NTFS partitions the way that WSL1 does.
+ NB rsync doesn't work with NTFS partitions the way that WSL1 does.
Read WSL & Visual Studio Code and go back and read the bits about VS Code
running remotely in the ※Windows data maintenance laptop page.
@@ -57,10 +58,13 @@ permissions that are fundamentally different things and are never in sync in any
href="https://devblogs.microsoft.com/commandline/chmod-chown-wsl-improvements/">All sorts of fun results. The alternative is to store all your data
in the \\wsl$\ ext4 filesystem (WSL2 only, not WSL1).
- If you are disturbed by the instructions to produce an entirely different key for WSL to use when your PC already has a perfectly good PuTTy key installed on the server, then you are right. It is inelegant. But it works, the instructions are shorter and there are fewer things that go wrong. If you are terribly offended by that then you can set your PC up to use one key shared between WSL and normal-Windows as described in this October 2019 article. (Don't set up a password on the key because then you don't need to install keychain.) But beware, this sort of thing goes out of date quite rapidly.
+ If you are disturbed by the instructions to produce an entirely different SSL key for WSL to use when your PC already has a perfectly good PuTTy key installed on the server, then you are right. It is inelegant. But it works, the instructions are shorter and there are fewer things that go wrong. If you are terribly offended by that then you can set your PC up to use one key shared between WSL and normal-Windows as described in this October 2019 article. (Don't set up a password on the key because then you don't need to install keychain.) But beware, this sort of thing goes out of date quite rapidly.
If you have PuTTY installed and working, but you now want to use WSL rsync, you need to set up a key again within the WSL environment. So on a machine with WSL enabled, create an ordinary cmd window and get into the WSL environment using the wsl command: If you have PuTTY installed and working, but you now want to use WSL rsync, you need to set up a key again within the WSL environment.
+ [ Now that Microsoft allows installation of OpenSSL using standard Windows tools on Windows 10 and 11, we need someone to revise all the Windows/troggle documentation for a PuTty-free route. Volunteers? ]
+
+ So on a machine with WSL enabled, create an ordinary cmd window and get into the WSL environment using the wsl command: WSL2 installs python by default, but it may be a rather old python (depending on the history of your laptop, phase of moon etc.) and if you want development speed you want python3.11. [NB the expo server currently runs python 3.9, so don't use any post3.9 idioms in your code.]
+ To install python3.11 and pip follow these instructions to the letter. But that's not enough, you need to configure pip to work properly with python3.11 (this is because it's a bit bleeding edge as yet), so you ALSO then need to re-install the latest with:
+ The error you are trying to get rid of when attempting to use pip looks like this:WSL - Creating another ssh key
-
+
D:\CUCC-Expo\expoweb\ wsl
@@ -158,7 +162,19 @@ and heremount-usb-drives-windows-subsystem-for-linux
ssh command line
+ The pain continues: Python on WSL2
+
+curl -sS https://bootstrap.pypa.io/get-pip.py | python3.11
+and test the result using:
+
+python3.11 -m pip --version
+
+ ImportError: cannot import name 'html5lib' from ...
Go back to: ※Basic laptop
Go back to: ⁂Survey laptop