Am I the only one who thinks this was named backwards?
Like, it should been: Linux Subsystem for Windows, or maybe Windows' Subsystem for Linux
Windows Subsystem for Linux 2 Moving into General Availability
61–70 of 420 posts
Re: Windows Subsystem for Linux 2 Moving into General Availability
#62Does anyone know if WSL2 supports utf8 characters in filenames, such as ":" and "" etc?
WSL had a limitation that it couldn't display such characters when I accessed a Linux parition through Samba. I know there is a Samba workaround for name mangling, but I prefer to access the actual filenames as created by org-mode.
Edit: Samba was running in an Alpine VM that mounted a ZFS partition. The network folder was mounted through Windows.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#63So WSL2 is supported on windows 10 Home as well, which is great. Does that mean Home also gets official Hyper V support?
I don't see any mention that it'll be on Home, "General Availability" just means that it's no longer part of the insider preview
Re: Windows Subsystem for Linux 2 Moving into General Availability
#64I am giving up. WSL1 was a great invention but Microsoft gave up on it, either because of the filesystem performance problems or because of the debuggers. https://github.com/microsoft/WSL/issues/2028 (lldb, rr, delve all affected). This looks like a dreaded case of the first 90% is easy, it's the second 90% that is hard. Imagine implementing a translator for a vast majority of Linux syscalls just to find certain flav…
I guess it's subjective. I've been using Linux on Windows 10 pretty successfully for a year now to do some things that would otherwise be much more inconvenient.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#65Have they figured out how to pass through the GPU yet? Would be cool to use this for e.g. PyTorch.
Unfortunately no. This would have been a very useful feature to me since currently I use a Windows laptop to write code to run on a linux gpu server under my desk.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#66Am I the only one who thinks this was named backwards? Like, it should been: Linux Subsystem for Windows , or maybe Windows' Subsystem for Linux
Totally agree. Feels like a “windows has to be first” type of thing.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#67I am giving up. WSL1 was a great invention but Microsoft gave up on it, either because of the filesystem performance problems or because of the debuggers. https://github.com/microsoft/WSL/issues/2028 (lldb, rr, delve all affected). This looks like a dreaded case of the first 90% is easy, it's the second 90% that is hard. Imagine implementing a translator for a vast majority of Linux syscalls just to find certain flav…
WSL was very cool from a pure tech standpoint, but I've never been clear what the actual use case for it was. WSL2 seems to be more along the lines of coLinux, which I felt the same way about when it was new.
Re: Windows Subsystem for Linux 2 Moving into General Availability
#68So WSL2 is supported on windows 10 Home as well, which is great. Does that mean Home also gets official Hyper V support?
I don't see any mention that it'll be on Home, "General Availability" just means that it's no longer part of the insider preview
According to FAQ [1] it will be.
[1] https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq#does-w...
Re: Windows Subsystem for Linux 2 Moving into General Availability
#69the performance on /mnt issue is not yet fixed https://github.com/microsoft/WSL/issues/4197
Re: Windows Subsystem for Linux 2 Moving into General Availability
#70How does this work with IDEs like IntelliJ? I believe WSL 1 had issues with having Windows IntelliJ and the source code being in WSL?
Works just fine, but FS is slow-ish. Your paths look like:
\\wsl$\Ubuntu-18.04\home\username