Testing the Windows Subsystem for Linux

#1

Post by jackhammons » Tue, Apr 11, 2017, 9:21 PM UTC

Testing the Windows Subsystem for Linux
blogs.msdn.microsoft.com

Re: Testing the Windows Subsystem for Linux

#2

Post by ape4 » Tue, Apr 11, 2017, 11:43 PM UTC

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

Re: Testing the Windows Subsystem for Linux

#3

Post by dragonwriter » Tue, Apr 11, 2017, 11:49 PM UTC

ape4 wrote: 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.

Re: Testing the Windows Subsystem for Linux

#4

Post by yarrel » Tue, Apr 11, 2017, 11:52 PM UTC

dragonwriter wrote: post #3

ape4 wrote: 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.

Yes that still doesn't work.

Re: Testing the Windows Subsystem for Linux

#5

Post by TillE » Tue, Apr 11, 2017, 11:54 PM UTC

dragonwriter wrote: post #3

ape4 wrote: 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.

But that (a subsystem "for Linux") would only be referring to the small compatibility layer for syscalls and stuff, rather than the whole Bash environment which "WSL" typically means.

Re: Testing the Windows Subsystem for Linux

#6

Post by mixmastamyk » Tue, Apr 11, 2017, 11:55 PM UTC

ape4 wrote: post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

MS is horrible at naming things, WOW64 anyone?

Re: Testing the Windows Subsystem for Linux

#7

Post by GhotiFish » Wed, Apr 12, 2017, 12:03 AM UTC

dragonwriter wrote: post #3

ape4 wrote: 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.

Windows Subsystem's Not Unix.

Re: Testing the Windows Subsystem for Linux

#8

Post by akulbe » Wed, Apr 12, 2017, 12:14 AM UTC

ape4 wrote: post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

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

Re: Testing the Windows Subsystem for Linux

#9

Post by milcron » Wed, Apr 12, 2017, 12:16 AM UTC

ape4 wrote: post #2

I still have a hard time with bash-backwards name: "Windows Subsystem for Linux". Its a Linux subsystem for Windows.

Better than "Bash on Ubuntu on Windows".

Re: Testing the Windows Subsystem for Linux

#10

Post by hdhzy » Wed, Apr 12, 2017, 12:17 AM UTC

ape4 wrote: 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...