Live data from Hacker News

Testing the Windows Subsystem for Linux

blogs.msdn.microsoft.com

31–40 of 142 posts

Re: Testing the Windows Subsystem for Linux

#31
post #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.

We maintain a fork of LTP internally. Eventually we hope to contribute our changes back but unfortunately open sourcing isn't free and we have bigger fish to fry[1].

[1] https://wpdev.uservoice.com/forums/266908-command-prompt-con...

Re: Testing the Windows Subsystem for Linux

#32

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?

Nope.

It traps the software interrupt which initiates a system call under Linux and the Windows kernel takes over, emulating that system call.

Re: Testing the Windows Subsystem for Linux

#34
post #15
post #8

Earlier quoted context omitted.

It's still the Windows kernel. No Linux kernel here. Just Linux userspace. The name may not sound good, but it's technically accurate. :)

Maybe it should be Windows subsystem for GNU

Or 'GNU/NT' if we heed the purists who insist on saying 'GNU/Linux'. Not sure how to pronounce that...

Re: Testing the Windows Subsystem for Linux

#35

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

[deleted]

Re: Testing the Windows Subsystem for Linux

#36

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

That's exactly backwards. They're doing a reasonable but very late job of modernizing their user space on top of their quite decent kernel, including giving a Linux environment for those that want it. I for one respect them for that, even though I've been almost exclusively a Linux user since the early 90s. Lately installed Windows 10 and TBH between powershell and improved command line facilities, improvements to the windows GUI itself, and the linux subsystem it's not bad at all these days.

Re: Testing the Windows Subsystem for Linux

#37
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...

How about "Windex"? Oh wait ...

Re: Testing the Windows Subsystem for Linux

#38
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...

I thought that both "Windows" and "Linux" were trademarks?

Re: Testing the Windows Subsystem for Linux

#39

Earlier quoted context omitted.

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.

Windows Subsystem's Not Unix.

... which might fit well with IBM's not quite Unix thing AIX, which acquired the nickname "Ain't unIX".
Post reply on HN