Live data from Hacker News

Testing the Windows Subsystem for Linux

blogs.msdn.microsoft.com

111–120 of 142 posts

Re: Testing the Windows Subsystem for Linux

#111

Earlier quoted context omitted.

You can say that about Linux as well; the bread-and-butter of the CLI experience is still the GNU stuff. EDIT: Yes, there are non-GNU Linux distributions, but WSL is based off Ubuntu specifically and ships with a GNU userland by default.

What if you run a ToyBox userland then? Or BusyBox for that matter

What if your run ToyBox on Ubuntu? You have a lot of work to do upfront and get less functionality in return.

Re: Testing the Windows Subsystem for Linux

#112

Earlier quoted context omitted.

You can say that about Linux as well; the bread-and-butter of the CLI experience is still the GNU stuff. EDIT: Yes, there are non-GNU Linux distributions, but WSL is based off Ubuntu specifically and ships with a GNU userland by default.

What if you run a ToyBox userland then? Or BusyBox for that matter

[deleted]

Re: Testing the Windows Subsystem for Linux

#113

Can we get the new, improved subsystem without having to go through the Win10 Creator's Update?

Why not go through Windows 10 Creator's Update?

Apart from the new .NET Framework 4.7 and a few minor others, a bunch of features (e.g. Paint 3D) are not necessarily targeted towards advanced users. It would make sense to fragment some key modules we use as devs and make those available piecemeal without bundling features we'll probably never use with great features like WSL and the new Windows console. Essentially MS could give options just like it gives options about what to install on VS 2017 (for advanced users of course, regular users can have the default CU install mode).

Re: Testing the Windows Subsystem for Linux

#114

I'd just like to interject for moment. What you're refering to as WSL, is in fact, GNU/NT, or as I've recently taken to calling it, GNU plus NT. NT is not an operating system unto itself, but rather a non-free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX. Many computer users run a modified version of t…

In all seriousness (your message could be in favor of, hostile to, or neutral toward GNU; I can't be sure), I got rms' opinion on all of this in April of last year and wrote about it: https://mikegerwitz.com/2016/04/GNU-kWindows (He proofread, and I made suggested changes.)

I feel like I've read that before.

I'm a supporter of the GNU project but I'm very ambivalent about its communication strategy. I posted this because I think it's as true for GNU/NT as it is for Ubuntu, which is... technically true, but hard to talk about without sounding off-putting.

Re: Testing the Windows Subsystem for Linux

#115

Earlier quoted context omitted.

You can say that about Linux as well; the bread-and-butter of the CLI experience is still the GNU stuff. EDIT: Yes, there are non-GNU Linux distributions, but WSL is based off Ubuntu specifically and ships with a GNU userland by default.

There are Linux distributions which contain almost no GNU software, e.g. Alpine Linux which is built around musl libc and busybox: https://alpinelinux.org/about/

WSL is "Ubuntu GNU/NT". You can't base your WSL install off other distros AFAIK.

Re: Testing the Windows Subsystem for Linux

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

Shouldn't that be Windows' Linux Subsystem?

Re: Testing the Windows Subsystem for Linux

#117

Earlier quoted context omitted.

There are Linux distributions which contain almost no GNU software, e.g. Alpine Linux which is built around musl libc and busybox: https://alpinelinux.org/about/

WSL is "Ubuntu GNU/NT". You can't base your WSL install off other distros AFAIK.

It takes a little work, but SuSE can work with WSL too: https://www.suse.com/communities/blog/make-windows-green-par...

Re: Testing the Windows Subsystem for Linux

#118
post #25

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.

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.

it's the subsystem for running Linux. It's not actually Linux, and after enabling the subsystem you still have to actually get the Ubutntu image. That image is the Linux part.

Re: Testing the Windows Subsystem for Linux

#119
Although I love their work, unfortunately the terminal (window cmd bash) is horrible. Copy and Paste is a pain, doing panel splits are impossible unless you use tools like tmux.

I would love to see terminator or a more advanced terminal.

Re: Testing the Windows Subsystem for Linux

#120

Earlier quoted context omitted.

> developer tools, most of which are GNU software? such as python, nodejs, elixir and PHP?

You can say that about Linux as well; the bread-and-butter of the CLI experience is still the GNU stuff. EDIT: Yes, there are non-GNU Linux distributions, but WSL is based off Ubuntu specifically and ships with a GNU userland by default.

I feel that you miss the point of WSL. Bash and coreutils have worked on Windows for years. In fact, they ship with git so most developers have had them for years.

The point is compatibility much more than CLI UX. The ability to run that nodejs or Python project even though one of the 1352 subsubsubdependencies has a bug on Windows.

Post reply on HN