Live data from Hacker News

Testing the Windows Subsystem for Linux

blogs.msdn.microsoft.com

21–30 of 142 posts

Re: Testing the Windows Subsystem for Linux

#21

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?

It uses a Linux-compatible kernel interface with no Linux kernel code plus Ubuntu's userland. I guess that's why they sometimes call it Bash on Windows. I'm surprised no one's proposed "Windows Subsystem for GNU".

Re: Testing the Windows Subsystem for Linux

#22
post #10
post #2

I 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...

In that case Windows Linux Subsystem seems like a good compromise.

Re: Testing the Windows Subsystem for Linux

#23
Wake 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

#24

Using the unit tests of other Linux software to be your own compatibility test is delightful. It almost feels a little subversive.

>In these cases, the WSL team covers test gaps by writing our own unit tests. At time of writing the team has written over 150,000 lines of unit test code for systems calls and virtual files (/proc, /sys).

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

#25
post #2

I 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.

Yeah it's the 'for' in there that makes it wrong. It's not 'for' Linux, it's for Windows. I know what it is and I _still_ think of it backwards every time I read it.

Re: Testing the Windows Subsystem for Linux

#27
post #14

Earlier 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-…

I guess it is Visual Studio 15 (as in version 15), and that still holds.

Re: Testing the Windows Subsystem for Linux

#28

Wake 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) :)

Why would they do that? NT is a very good kernel design.

Re: Testing the Windows Subsystem for Linux

#29
post #22
post #10

Earlier 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.

It's never going to happen.

:(

Re: Testing the Windows Subsystem for Linux

#30
post #2

I 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.

This explains one interpretation but it doesn't excuse the ambiguity.
Post reply on HN