I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Which is why I have a GNU/Windows sticker on my laptop.
Testing the Windows Subsystem for Linux
41–50 of 142 posts
Re: Testing the Windows Subsystem for Linux
#42Earlier quoted context omitted.
> 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...
That's understandable. Thanks for the reply.
Out of curiosity, is progress on WSL bound by any blocking issues in particular, or could your team benefit from more resources being assigned to the project?
Maybe I'm naïve, but I tend to view WSL as a perfect way to win over a ton of developers who are becoming disillusioned with macOS, but are hesitant to run bare metal Linux due to the headaches involved (insofar that macOS and Windows "just work").
Re: Testing the Windows Subsystem for Linux
#43Re: Testing the Windows Subsystem for Linux
#44I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
They could use Windows Linux Subsystem.
Re: Testing the Windows Subsystem for Linux
#45Earlier 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...
I thought that both "Windows" and "Linux" were trademarks?
Presumably Microsoft is allowed to use Windows wherever they please ;)
Re: Testing the Windows Subsystem for Linux
#46Wake 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) :)
You've "read" wrong. The NT kernel has seen major changes up through and including W10, including focusing on power management and efficiency, improving modularity, and memory use.
It seems like your comment was meant to troll, but in the odd chance you're interested, you can follow a lot of these changes and the decisions behind them where Microsoft documented the process on the old Engineering Windows blog, and well as more recently at the main Windows blog itself.
Re: Testing the Windows Subsystem for Linux
#47Wake 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 how SQL Server on Linux works...
https://arstechnica.com/information-technology/2016/12/how-a...
Re: Testing the Windows Subsystem for Linux
#48I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.
Then why not Windows's Linux Subsystem?
Re: Testing the Windows Subsystem for Linux
#49Is anyone here using this for *Nix traditional tools?
Mostly curious about Vim/Tmux, and having serve operations spit out the server into the actual Windows browser?
I did read something about the creator update adding 24 color support.
Re: Testing the Windows Subsystem for Linux
#50Does anyone use this for work? Could I replace Ubuntu with Windows now?
I use it on my laptop and am generally very happy with it, although I don't do all that much technical work there and certainly wouldn't want it to replace my primary workstation. (I'd be dearly sad if I had to give up xmonad.)
But it's made my laptop a far more pleasant place to get work done if I need to do so, and generally works far better than I was expecting it would. I no longer feel compelled to run a VM on my laptop to get real work done.