Anyone managed to get the latest WSL 2 update?
I didn't know there was a specific update -- link? @didibus
(I'm on Windows 10 21313 which is the latest Insider Dev Channel build I believe -- and I think we get WSL2 updates as part of that?)
Are you referring to this update from September? I don't see a more recent version listed on the blog. https://devblogs.microsoft.com/commandline/whats-new-in-the-windows-subsystem-for-linux-september-2020/
I read there's an update, but can't find it
It seems my internet from WSL 2 stopped working, so was hoping to try an update
Looks like my WSL2 install was all updated on Feb 10th -- but that's almost certainly part of an Insider update to Windows itself, given that the last public update I can find documented is from September...?
Ya, its possible I read something speaking of an insider update
Hum, weird ok it works again now
I do seem to recall some issue mentioned where WSL2 was losing Internet connectivity and it got fixed -- but it's hard to keep track of which build stream gets which fixes TBH. I've been on Insider builds for about six years (nearly always Fast Ring / Dev although I occasionally back off to Slow Ring / Beta).
(hard to keep track because I really only pay attention to the dev builds -- same with Edge: I'm on the Canary/Dev channel for that as well on every machine)
Ya, internet connectivity has been my biggest issue with WSL 2 till now
I keep having to Disable Large Send Offload on the vEthernet adapter.
Also, when my computer Sleeps, the X server breaks
That one is annoying, cause it kills Emacs, and if I forgot to save something, I lose it :S
How about run a emacs server in WSL? If X is down, the emacs server is still running.
@didibus I've heard people complain about that (X server not surviving sleep) but I can't say that I've ever had that happen. I run Reveal via VcXsrv from WSL2 and it's been running on my machine for days through numerous sleep/restart cycles.
My dev setup on Windows/WSL2 is VS Code (on the Windows side) with all the extensions managed via its WSL2-Remote process, with Socket REPLs started on the Ubuntu side, running Reveal via VcXsrv. Seems rock solid. Runs for days with at least one sleep/restart per day.
Hum... good point, I thought I did have that setup for my Emacs, but I think WSL 2 shutdowns or something weird
(not quite as long as the REPL on my Mac desktop which I started on January 31st 🙂 )
I'm using X410, maybe switching to VcXsrv would help
VcXsrv/Xlaunch has been awesome for me...