I'm particularly eager to see WSL allow GPU pass-through so I can use PyTorch without a VM or dual-boot on my work computer.
I don't think that's necessary. WSL runs Linux binaries directly, it should use the host GPU just like any Windows program.
Windows Subsystem for Linux on Windows Server
41–50 of 67 posts
Re: Windows Subsystem for Linux on Windows Server
#42Earlier quoted context omitted.
See, as much as it's a meme at this point, this is really where the GNU/Linux distinction is important. WSL is really GNU/Windows which is probably horrifying and a massive success story for the FSF.
Can you clarify the GNU/Linux distinction with regard to the WSL? I mean... isn't the main WSL layer a flavor of Ubuntu?
Linux is the name of the kernel. It is also used as the name of the kernel plus the userland, which has a lot of GNU code in it (although give Poettering some time and we'll see). WSL is the userland without the kernel.
Re: Windows Subsystem for Linux on Windows Server
#43I've been using WSL on Windows 10 since it's release. I'd love to know the inside story of how it came to be. A lot of companies would never try something like this. For me WSL has worked as perfect as could be expected, nothing failed to run that I need yet. The gaps are being slowly closed (e.g. executing between WSL/Windows). I no longer have to develop in a VM, nor be forced to use a Mac just because it has "unix…
Well, I'd love to use it if the I/O would improve. At the moment I just use Cygwin instead.
What are the problems with I/O? I am looking at this thread with an eye on buying a windows laptop for dev. instead of a mac.
Re: Windows Subsystem for Linux on Windows Server
#44> "you cannot currently use WSL to run persistent Linux services, daemons, jobs, etc. as background tasks." Still, this has me wondering if that's the ultimate goal here. Is Microsoft trying to position Windows 10 as a high quality Linux server in the long-term?
That's something I look forward to. Does anyone know of a solution of reliable SFTP on windows? By SFTP I mean copy-over-ssh as opposed to FTP with TLS. So I guess I'm asking for a standard sshd running as a windows service.
Ubuntu on WSL lets you run sshd. You can get to your Windows file system at /mnt/c/.
Re: Windows Subsystem for Linux on Windows Server
#45Earlier quoted context omitted.
Well, I'd love to use it if the I/O would improve. At the moment I just use Cygwin instead.
What are the problems with I/O? I am looking at this thread with an eye on buying a windows laptop for dev. instead of a mac.
It is very slow. Like noticeably slow. Especially if it comes to stuff like rsync and a lot of files. If you just use vim and such you would probably not notice it as much.
Also depending on how you develop you might run into unsupported things. For example, I once tried to run IntelliJ Linux version on it through X11 Forwarding. Didn't really run perfectly.
So right now I am too afraid to develop in it because what if the real Linux acts differently? I guess you could always test it, but then why not just develop in Linux already?
Re: Windows Subsystem for Linux on Windows Server
#46Earlier quoted context omitted.
this is not the first time microsoft has done this. https://en.wikipedia.org/wiki/Windows_Services_for_UNIX one could even argue they are somewhere between the embrace and extend phase.
> one could even argue they are somewhere between the embrace and extend phase. I see it more as grasping at straws to stay relevant. The Ballmer-era FUD campaign was mostly a failure (and bad PR). "If you can't beat 'em, join 'em".
With Pichai they're steering more towards a service-oriented company. Linux clearly has a place in their vision. You can see this also in their offerings on Azure.
Microsoft is a large company. In recent years, many *NIX developers joined them. Although I don't have statistics.
Gone are the days where its funny or righteous to bash Microsoft on /. heck gone is /.
Its also not only Microsoft; its Wintel at a whole. Desktop market lost a lot of its relative relevance. Intel is also having trouble with ARM platform [1]. That's not only desktop market. ARM's onto the server market as well.
I'm not really backing the above up with sources and numbers though so take it with a grain of salt.
[1] https://www.fool.com/investing/general/2014/12/02/intel-corp...
Re: Windows Subsystem for Linux on Windows Server
#47I'm particularly eager to see WSL allow GPU pass-through so I can use PyTorch without a VM or dual-boot on my work computer.
I don't think that's necessary. WSL runs Linux binaries directly, it should use the host GPU just like any Windows program.
It doesn't work, because Linux GPU drivers don't run on the WSL (fake) Linux kernel.
Re: Windows Subsystem for Linux on Windows Server
#48I'm particularly eager to see WSL allow GPU pass-through so I can use PyTorch without a VM or dual-boot on my work computer.
They mention in some blog post that this is not gonna happen very soon.
Re: Windows Subsystem for Linux on Windows Server
#49Earlier quoted context omitted.
Not really because what Microsoft is doing is actually GNU/Windows. Google is busy with ChromeOS/Linux and Android/Linux. Apple keeps developing their NeXTSTEP/BSD derivative.
This is actually really interesting. Google doesn't have a kernel so they're borrowing Linux. Microsoft doesn't have a good developer userspace so they're borrowing GNU's.
Not all Windows developers agree with that, though.
Re: Windows Subsystem for Linux on Windows Server
#50Earlier quoted context omitted.
See, as much as it's a meme at this point, this is really where the GNU/Linux distinction is important. WSL is really GNU/Windows which is probably horrifying and a massive success story for the FSF.
Can you clarify the GNU/Linux distinction with regard to the WSL? I mean... isn't the main WSL layer a flavor of Ubuntu?
WSL is running Ubuntu software with the GNU userspace on top of the Windows kernel using a Linux translation layer.