I like the idea of the Linux Test Project. Neat. I'm curious, does the WSL actually use any parts of Linux under the hood, or is it just an emulation of the user space, like Cygwin?
Testing the Windows Subsystem for Linux
21–30 of 142 posts
Re: Testing the Windows Subsystem for Linux
#22I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Yes, but names starting with a trademark are a no-no. See [0] (bitcrazed works on WSL) and [1]. Also IANAL. [0]: https://news.ycombinator.com/item?id=13697918 [1]: https://www.andreas-jung.com/contents/dont-use-docker-in-git...
Re: Testing the Windows Subsystem for Linux
#23Re: Testing the Windows Subsystem for Linux
#24Using the unit tests of other Linux software to be your own compatibility test is delightful. It almost feels a little subversive.
I wonder why they went that route instead of contributing to LTP directly?
While there's probably some edge cases specific to WSL, surely much of their increased unit test coverage would be applicable beyond WSL.
Re: Testing the Windows Subsystem for Linux
#25I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
It's a subsystem of Windows (hence Windows Subsystem). And, among all Windows Subsystems, it's the one for Linux, hence Windows Subsystem for Linux.
Re: Testing the Windows Subsystem for Linux
#26I like the idea of the Linux Test Project. Neat. I'm curious, does the WSL actually use any parts of Linux under the hood, or is it just an emulation of the user space, like Cygwin?
Re: Testing the Windows Subsystem for Linux
#27Earlier quoted context omitted.
MS is horrible at naming things, WOW64 anyone?
Or the needless confusion when everything needed to have .NET tacked onto the name. Or after they bought Skype, and rebranded the unrelated Lync as Skype for Business. Not to mention that Lync is a homophone of LINQ, which was coming out around when Office Communication Server became Lync... Or lately, when you had Visual Studio 2015, and what is now Visual Studio 2017 being called Visual Studio '15 while it was pre-…
Re: Testing the Windows Subsystem for Linux
#28Wake me when MS offers Linux subsystem for Windows (basically commercial WINE). From what I have read, MS is not actually that interested in improving the Windows kernel anymore unless needed or profitable. Why don't they give up and run windows user space on Linux (or BSD) :)
Re: Testing the Windows Subsystem for Linux
#29Earlier quoted context omitted.
Yes, but names starting with a trademark are a no-no. See [0] (bitcrazed works on WSL) and [1]. Also IANAL. [0]: https://news.ycombinator.com/item?id=13697918 [1]: https://www.andreas-jung.com/contents/dont-use-docker-in-git...
In that case Windows Linux Subsystem seems like a good compromise.
:(
Re: Testing the Windows Subsystem for Linux
#30I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
It's a subsystem of Windows (hence Windows Subsystem). And, among all Windows Subsystems, it's the one for Linux, hence Windows Subsystem for Linux.