The apt name would be Microsoft/Linux. But that would give Stallman an aneurysm.
WSL 1 was GNU/NT, I would think.
..and that would give him the final blow.
Microsoft's Linux Kernel
201–210 of 532 posts
Re: Microsoft's Linux Kernel
#202Earlier quoted context omitted.
It can be pretty easily applied to GPLv2 in commercial agreement. "You get the source under GPL and all the rights, but if you publish anything, you're dead to us and you need our product". This is what grsecurity does with Linux kernel, but the extinguish part is not in their interest.
This post is literally a link to the source code published on Github, and the commits aren't obfuscated either.
My explanation was unrelated to this specific code. You asked for how it can be done with this license.
Re: Microsoft's Linux Kernel
#203I admire what Microsoft have done with WSL and now WSL2, it's really pretty cool. Satya has done an excellent job revitalizing Microsoft from the Ballmer days. However, WTF. Why has the "Microsoft" directory got a leading capital. I mean every.other.directory.in.linux.is.lower.case!!!!!! Look around folks! Every other vendor in that tree has their name lowercase, please respect the local customs!
Because it’s an English proper noun?
Re: Microsoft's Linux Kernel
#204Earlier quoted context omitted.
Windows Subsystem for Linux is really close to that though. If you have not tried it yet you can download a Windows VM for developers from Microsoft that includes WSL and other dev goodies. Its mostly for evaluation but good enough to get started with. Edit: Here is the link to the Microsoft provided VMs: https://developer.microsoft.com/en-us/windows/downloads/virt...
This is still with Linux running in a VM though, right? I'd like a lightweight VM for legacy Windows and Linux running on metal. Given Microsoft's zeal for legacy support I'd say there's a snowball's chance in hell for this, but a man can dream.
Iirc, even the Win32 APIs sit above the subsystem layer. There was the OS/2 subsystem back in the day, Win32, and one more I can’t remember from my training 11 years ago.
Re: Microsoft's Linux Kernel
#205Earlier quoted context omitted.
Exactly. Linux won on technical merits, but we failed to educate people about the really important part about freedom.
> Linux won on technical merits Arguably. It's hard to say Linux won on technical merits of networking compared to FreeBSD or OpenBSD, or on storage compared to FreeBSD+ZFS, or say that generally when devs chose MacOS X. I suggest Linux won for being: the most popular out of the things which cost $0. BSD lost for not being popular, commercial Unix, Windows and MacOS lost for costing money.
> BSD lost for not being popular
People used to say that BSD lost because of the ambiguous copyright status of the early 90s, allowing Linux to glide in unopposed as the "free unix-like os for PCs".
https://en.wikipedia.org/wiki/UNIX_System_Laboratories,_Inc.....
https://en.wikipedia.org/wiki/Berkeley_Software_Distribution...
Re: Microsoft's Linux Kernel
#206Well that is pretty nice. WSL gets that much more exactly like Linux. What I really appreciate about WSL is that you get the accessibility of a bunch of OSS projects and a machine which has legit drivers for all of its component bits. What this means to me is that searching for a "linux laptop" won't be a chore, if it runs the latest Windows it will run Linux. And I can do development on the Linux side while communic…
There are a few annoyances with WSL2. For me the most important are: 1. You can't connect to a port listening on WSL localhost like in WSL1, you have to figure out the WSL IP address and use that. 2. From WSL you can't connect to a Windows TCP port on localhost, you must figure out the Windows IP (cat /etc/resolv.conf) and use that. 3. The WSL remote interpreter on PyCharm is not working anymore. The suggested workar…
The WSL team knows about this issue and I think they hope to fix it before it ships in Windows stable.
Re: Microsoft's Linux Kernel
#207Well that is pretty nice. WSL gets that much more exactly like Linux. What I really appreciate about WSL is that you get the accessibility of a bunch of OSS projects and a machine which has legit drivers for all of its component bits. What this means to me is that searching for a "linux laptop" won't be a chore, if it runs the latest Windows it will run Linux. And I can do development on the Linux side while communic…
So how do the drivers work? Is Microsoft implementing and integrating cross platform drivers? Have they somehow made Linux a microkernel that uses windows drivers through a shim?
Re: Microsoft's Linux Kernel
#208Earlier quoted context omitted.
As of VirtualBox 6.0, they should be able to coexist (because VirtualBox piggies onto Hyper-V when it’s enabled effectively).
In practice it's not really working though. At least not yet. There's a very long thread on virtualbox forums with people trying to get it to work but failing. I personally have to reboot when I need to use docker or virtualbox. Very annoying.
Yep, this is currently confirmed broken on Windows 10 1903 (Windows Hypervisor Platform extended user-mode APIs). Affects VirtualBox, qemu, etc. We may see a patch, but it's up in the air right now. (, I know.)
Re: Microsoft's Linux Kernel
#209Re: Microsoft's Linux Kernel
#210Earlier quoted context omitted.
Disclosure: I work at Microsoft but not on Windows (and my work machine is a MacBook Pro FWIW) WSL 2 is a lot like that -- it's a VM in the sense that it uses Hyper-V, but it's super lightweight. And in fact, when WSL 2 is enabled, both Windows AND Linux are running in the same type of VM (separate, obviously), so it's near-native performance in a lot of ways. There are still some I/O issues that the team is actively…
> There are still some I/O issues that the team is actively working on, but early benchmarks are quite promising. =/ Hoping to run my R code on WSL 2. Glad I got the answer. I wish you guys well on I/O issues. Is there any performance hit for WSL2 in regard to process forking? I recall that how window and unix deal with process is different (my R code uses mclapply parallel package for unix). I'm curious if there wil…
On Reddit, they had a benchmark for WSL1 vs WSL2 and it showed that the Single core perf of WSL2 was sometimes better than Windows (and even bare metal linux - how that happened I am not sure). The multi-core was not as good, but still better than WSL1.
I can't find that exact thread right now, but here's another one comparing WSL with Windows:
https://www.reddit.com/r/bashonubuntuonwindows/comments/c1r6...