expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-29 05:11:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

wsl1 - online edit of handbook/computing/wsllaptop.html

Browse Source
This commit is contained in:
Expo on server 2024-04-16 02:43:44 +01:00
parent bc7c7e046f
commit 63651db766
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
handbook/computing/wsllaptop.html
View File

@ -25,8 +25,8 @@ In late 2022 a new way of <a href="https://www.theregister.com/2022/11/23/wsl_
installing and using WSL</a> was announced and this page has been revised to match. <a href="https://learn.microsoft.com/en-us/windows/wsl/compare-versions?source=recommendations">WSL2 is now noticeably even slower</a> for NTFS files, so now it is only really useable if you move all the troggle code into your Linux filespace on <var>\\wsl.localhost\Ubuntu-22.04\home</var> which means that those files will only be accesible from Linux. Buggeration. If you have to use NTFS for those files for some other reason, you would need to revert to using WSL1.
<h3>WSL1 and WSL2</h3>
<p>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
been doing troggle development happily using WSL1.
This may be 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 had
been doing troggle development happily using WSL1. However time is clearly running out for WSL1, and the file handling is now very noticably slower. If your laptop won't run WSL2 then you are advised to get rid of Windows completely and install Xubuntu as a dual boot system.
<p>For some laptops though, WSL1 does not install properly and you have to use WSL2. The symptom is two error messages when you run <var>dmesg</var> in
the Linux bash terminal window. However, if all you want to use it for is rsync, this may still be fine.