News for hackers. Stuff that matters.
Re:DOS Subsystem for Linux by plus on Tuesday September 22, 2020 @12:41PM (#24556681)
There are a ton of comments here that seem to be misunderstanding what this software is. This creates a WSL-like environment on a DOS host system. It does not create a DOS environment on a Linux host. I'm not sure where this misunderstanding even comes from; the name is perfectly analogous to WSL.
Re:DOS Subsystem for Linux by iherbig on Tuesday September 22, 2020 @01:03PM (#24557010)
I would imagine it's because WSL is a terribly confusing name itself for a lot of people.

There are two ways to read "Windows Subsystem for Linux":

1. This is a subsystem that runs on Windows that enables Linux binaries.

2. This is a subsystem that runs on Linux that enables Windows binaries.

The confusion comes in the fact that when I write those two sentences, I naturally want to write "This is a subsystem FOR Windows..." or "This is a subsystem FOR Linux... ." I had to consciously avoid using "for" in that sentence to highlight the problem.

So when someone who doesn't know what the thing does reads "Windows Subsystem for Linux" they may walk away with the false impression that the subsystem allows Windows binaries to run on Linux. Likewise, what you're seeing now is that people are seeing "DOS Subsystem for Linux" and thinking that this enables you run DOS on Linux.

Re:DOS Subsystem for Linux by detaro on Tuesday September 22, 2020 @01:08PM (#24557075)
The WSL terminology really only makes sense if you are aware that Windows has the concept of subsystems - and which is why swapping other labels makes even less sense. I.e. the run-Windows-on-Linux thing would probably not be called Linux Subsystem for Windows, because what is a "Linux Subsystem"?

And of course WSL2 isn't a subsystem anymore, but is stuck with the product name. ¯\_(ツ)_/¯

Re:DOS Subsystem for Linux by Joker_vD on Tuesday September 22, 2020 @01:54PM (#24557692)
A "Linux subsystem" is a Linux system that is a part of a bigger system. And "Linux audio subsystem" is an audio system that is a part of Linux. And if you swap the words, you get "audio Linux subsystem" which doesn't make sense, not really.

So the proper name would be "Windows Linux subsystem", but I concede that it does sound really weird (because both Windows and Linux are the same kind of things, they're OSes).

And of course, if it was named "Windows's Subsystem for Linux", there would be much less confusion, but apparently the English for some reason doesn't use the possessive case here (although that's the perfect place for it) and prefer to use the noun as a possessive adjective.

Re:DOS Subsystem for Linux by hyperpape on Tuesday September 22, 2020 @02:43PM (#24558277)
This is helpful, but the composition rules are weird and confusing.

It's true that a Linux Subsystem is a subsystem of Linux, but an "X for Linux" is a component of Linux or an application for Linux.

When you put them together, it seems that the "for" wins the battle. In parsing terminology, it has lower precedence (though I'm sure the actual rules of English are more complex than that indicates).

I'd love to see an actual linguist comment on why this phrase is so confusing.

Re:DOS Subsystem for Linux by evilsnoopi3 on Tuesday September 22, 2020 @03:02PM (#24558479)
I have an English degree and can confidently say the issue is the implicit understood possessive in the correct parsing. As it stands, “for” dominates mentally because the phrase obviously needs a possessive to make sense and “for” denotes possession. If it were “Window’s Subsystem for Linux” or “DOS’s Subsystem for Linux”, explicating the proper possession, the parsing trouble would disappear.
Re:DOS Subsystem for Linux by waheoo on Tuesday September 22, 2020 @09:05PM (#24561878)
So would just saying Linux subsystem for windows.

Which was raised when this name came up but they didn't like that Linux came first so went with gymnastic language instead.

Its even more obvious with this new name.

Its a Linux subsystem for DOS.

Re:DOS Subsystem for Linux by Conan_Kudo on Tuesday September 22, 2020 @03:21PM (#24558657)
You could use the possessive form here: "Windows' Subsystem for Linux", but that's not a thing product managers like to use in naming...
Re:DOS Subsystem for Linux by kaidon on Wednesday September 23, 2020 @12:48AM (#24563078)
It probably had an internal name like "winix" or "lindows" - but PM took the reins and came up with a much worse name, as is tradition.
Re:DOS Subsystem for Linux by Joker_vD on Wednesday September 23, 2020 @04:59AM (#24564691)
Oh yes. My favourite example is [0] (and the parent twit).

[0] https://twitter.com/ericlippert/status/1205372172534874112

Re:DOS Subsystem for Linux by detaro on Tuesday September 22, 2020 @02:00PM (#24557775)
Oh, true, Linux actually uses the term in that context, somehow didn't think of that.
Re:DOS Subsystem for Linux by skissane on Tuesday September 22, 2020 @07:38PM (#24561307)
> And of course WSL2 isn't a subsystem anymore, but is stuck with the product name

Even WSL1 is not a classic Windows NT subsystem. Its implementation (picoprocesses) is quite different from that of the classic Windows NT subsystems (Win32, OS/2, POSIX/Interix/SFU/SUA). The classic Windows NT subsystems all involve using ntdll.dll to make NT syscalls; WSL1 processes make Linux syscalls and can't actually make NT syscalls or call ntdll. There is nothing technically stopping an OS/2 1.x executable from realising that it is running on NT and start talking to the NT kernel using the normal NT API; by contrast, a Linux executable running under WSL1, even if it detects it is running under WSL1, isn't allowed to talk to the normal NT kernel interfaces.

Re:DOS Subsystem for Linux by tinus_hn on Wednesday September 23, 2020 @06:33AM (#24565301)
Aren’t you describing personalities instead of subsystems?
Re:DOS Subsystem for Linux by skissane on Wednesday September 23, 2020 @03:47PM (#24571103)
Windows NT user mode code is divided into programs and subsystems.[1][2] Programs are the actual applications/utilities/etc you run. Subsystems are OS components executing in user mode, generally composed of DLLs and server EXEs which expose LPC services (a little bit like Unix daemons).

There are two types of subsystems – environment subsystems (which provide APIs to programs) and integral subsystems which provide services to the environment subsystems. Integral subsystems include the security subsystem (lsass.exe). (Sources are a bit unclear about whether there is one "integral subsystem" composed of multiple parts, or multiple integral subsystems – e.g. are lsass.exe and smss.exe separate integral subsystems, or two subsystems of the integral subsystem???)

There are three environment subsystems in Windows NT – Win32, POSIX and OS/2, although the latter two have been discontinued in newer versions. The design was always open to adding more (e.g. maybe an OpenVMS subsystem) but that never happened in practice. (Win32, despite its name, doesn't just run Win32, it also runs Win16 and DOS; also, in practice the POSIX and OS/2 subsystems were dependent on the Win32 subsystem and borrowed functionality from it, despite in theory being independent of it. csrss.exe, despite having "subsystem" in its name, is not a separate subsystem, but rather the primary LPC server for the Win32 environment subsystem.)

The term "personality" is sometimes used to describe the environment subsystems, but it is not the term the Windows NT developers used. The term "personality" actually comes from Mach. The idea with Mach was that existing operating systems could be ported to run on top of the Mach microkernel through layers called "personalities" which would map the existing OS API to the underlying Mach API. The original CMU Mach team built such a layer for BSD Unix – the BSD personality – and it actually survives in XNU (macOS/iOS/etc), but they never implemented any other personalities. However, IBM's abortive Workplace OS project actually did implement an OS/2 personality for Mach, which could run alongside an AIX personality, so they actually got closer to delivering on CMU's original vision (albeit the whole project was cancelled before being fully released.) Possibly, NT's environment subsystem idea took some influence from the Mach personality concept; plus, outside observers quickly noticed the similarity between NT environment subsystems and Mach personalities, and started using the term "personality" for the former; but it has never been the officially preferred terminology for Windows.

I've never heard anyone call WSL1 an "environment subsystem". Its method of implementation is very different from the classic NT environment subsystems. You might call WSL1 or WSL2 "personalities", but as I said that's never been official Windows terminology.

[1] https://en.wikipedia.org/wiki/Architecture_of_Windows_NT

[2] http://vig.pearsoned.com/samplechapter/0201791064.pdf

Re:DOS Subsystem for Linux by tobinfricke on Tuesday September 22, 2020 @01:11PM (#24557149)
I was under the impression that the name arose out of trademark requirements.

https://news.ycombinator.com/item?id=14093517

Re:DOS Subsystem for Linux by freeone3000 on Tuesday September 22, 2020 @01:18PM (#24557240)
Windows has had subsystems since the OS/2 era, and WSL1 was actually such a subsystem. Initrix was the Microsoft POSIX Subsystem.
Re:DOS Subsystem for Linux by EvanAnderson on Tuesday September 22, 2020 @02:09PM (#24557898)
There was a POSIX subsystem in Windows NT before Microsoft acquired Interix (which became Windows Services for Unix).
Re:DOS Subsystem for Linux by tobinfricke on Tuesday September 22, 2020 @06:06PM (#24560539)
Yes, but the name "Linux Subsystem for Windows" would have been much less confusing.
Re:DOS Subsystem for Linux by shawnz on Wednesday September 23, 2020 @01:41AM (#24563370)
WSL1 isn't actually an NT subsystem like Interix was.
Re:DOS Subsystem for Linux by dataflow on Tuesday September 22, 2020 @04:31PM (#24559529)
Could they have just called it the Windows Linux Subsystem?
Re:DOS Subsystem for Linux by knome on Tuesday September 22, 2020 @07:13PM (#24561110)
I assumed it was marketing. They didn't want to put the other guy's name first.
Re:DOS Subsystem for Linux by tenebrisalietum on Tuesday September 22, 2020 @06:49PM (#24560917)
And if you think "Windows Subsystem for Linux" is bad, the subsystem that enables the Win32 API is csrss or "Client/Server Runtime Subsystem" and it makes you think: why does that subsystem not mention Windows but the Linux one does?
Re:DOS Subsystem for Linux by p1necone on Tuesday September 22, 2020 @07:19PM (#24561172)
I have to assume the answer to that question is marketing. They really want to hammer into you that you're running Linux on Windows.
Re:DOS Subsystem for Linux by thesuperbigfrog on Wednesday September 23, 2020 @03:02AM (#24563853)
Agreed. "Linux on Windows" is more clear to me.

The "on Windows" part makes it clear that Windows is the host OS.

Many Microsoft's past products used "for $PLATFORM" in the product name. For example:

Microsoft Word for Windows

Microsoft Word for DOS

Microsoft Word for Mac

It makes it clear that it was the version of the product FOR a given platform.

At first glance "Windows Subsystem for Linux" seems like Microsoft's version of WINE.

Maybe we'll get a real "Windows Subsystem for Linux" when the desktop version of Microsoft Linux arrives.

Re:DOS Subsystem for Linux by kerng on Tuesday September 22, 2020 @06:49PM (#24560916)
Better choice would have been "Subsystem for Linux on Windows". Its all indeed a big naming confusion
Re:DOS Subsystem for Linux by stephen_g on Wednesday September 23, 2020 @02:13AM (#24563548)
It still doesn't even make sense when you know about Windows subsystems though. True, it is a "Windows subsystem" in Windows terminology, but from my native-English speaker point of view, it's not "for" Linux in the way that the word "for" is used in standard English.

It does work if you assume it's a shortening of something like "Windows Subsystem for Running Linux Applications (on Windows)"

But I get that naming it is a tricky problem, because even a technically accurate name like "Windows Linux Subsystem" (after the old 'Microsoft POSIX Subsystem' name) is still confusing.

Re:DOS Subsystem for Linux by kjaftaedi on Tuesday September 22, 2020 @02:30PM (#24558144)
It doesn't matter at all if you write 'for', as the possession is totally unclear.

"Windows Subsystem for Linux"

-----

Is the 'windows subsystem' for linux?

or is the 'subsystem for linux' a windows branded feature?

If you asked most people they would probably choose incorrectly.

Re:DOS Subsystem for Linux by city41 on Tuesday September 22, 2020 @02:15PM (#24557962)
As bad as the original name was, "Bash on Ubuntu on Windows", I think it was still better than WSL.
Re:DOS Subsystem for Linux by fomine3 on Tuesday September 22, 2020 @09:34PM (#24562024)
It's worse because it can run other distros and shells. hell.
Re:DOS Subsystem for Linux by pmontra on Tuesday September 22, 2020 @01:48PM (#24557627)
It's really confusing. Windows Linux Subsystem would be more clear. Windows Subsystem for Linux always hinted me to a Vine competitor. Then I know what it is so I read this DOS Subsystem for Linux in the right way (and right to left!)
Re:DOS Subsystem for Linux by dm319 on Tuesday September 22, 2020 @03:22PM (#24558678)
Also, why linux? Linux is the kernel, which is not what is being run, more like everything on a gnu/linux system apart from linux.
Re:DOS Subsystem for Linux by JdeBP on Tuesday September 22, 2020 @11:58PM (#24562803)
As I pointed out when WSL came out, the name always includes the thing that is being replaced by the Windows NT kernel: be that OS/2 or Linux.

* https://news.ycombinator.com/item?id=11417059

* https://news.ycombinator.com/item?id=18948258

Re:DOS Subsystem for Linux by black3r on Tuesday September 22, 2020 @05:07PM (#24559911)
WSL1 emulated Linux kernel syscalls. GNU was run on top of it unmodified, but could be used without GNU. on WSL2 the actual kernel is what is being run, in a thin VM wrapped by lots of wrappers to provide a native-like experience.
Re:DOS Subsystem for Linux by parliament32 on Tuesday September 22, 2020 @02:51PM (#24558365)
Why not use "in"/"on"?

Linux Subsystem on Windows

Linux Subsystem in Windows

Re:DOS Subsystem for Linux by kelnos on Tuesday September 22, 2020 @04:20PM (#24559365)
I expect Microsoft doesn't want to have "Linux" come first in the name from a branding perspective.
Re:DOS Subsystem for Linux by tracker1 on Wednesday September 23, 2020 @08:33AM (#24566234)
I saw a discussion that it was mostly concerns about the Linux trademark when WSL1 didn't actually use a Linux Kernel with the leading part of the name/term.
Re:DOS Subsystem for Linux by p1necone on Tuesday September 22, 2020 @07:17PM (#24561158)
Yep - the sentence "X subsystem for Y" reads to me like you're adding an X thing to your Y - i.e. you're adding some Windows thing to your Linux, but what Microsoft means by it is the other way around.
Re:DOS Subsystem for Linux by gegtik on Tuesday September 22, 2020 @01:08PM (#24557084)
Windows (Subsystem for Linux)

- vs -

Windows Subsystem (for Linux)

Re:DOS Subsystem for Linux by signal11 on Wednesday September 23, 2020 @02:44AM (#24563724)
((Windows Subsystem) for Linux)

is probably closest to WSL1’s intent.

It was a Windows subsystem (the first new one in years), and its goal was to let you run Linux apps.

Re:DOS Subsystem for Linux by derefr on Tuesday September 22, 2020 @03:06PM (#24558523)
"Windows Linux-ABI Subsystem" would have been crystal-clear.
Re:DOS Subsystem for Linux by zorked on Tuesday September 22, 2020 @03:10PM (#24558564)
Microsoft has a tradition with these confusing backwards names.

They used to have a product called Windows Services for UNIX [1] which was, you guessed it, UNIX Services for Windows: NFS, Telnet, cron, rsh, etc.

[1] https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

Re:DOS Subsystem for Linux by tracker1 on Wednesday September 23, 2020 @08:30AM (#24566203)
My understanding, especially with WSL1, was that there was a concern about the Linux trademark if MS used the name "Linux Subsystem for Windows" which would have been a better name, since WSL1 didn't actually use a Linux kernel. WSL2 does though.

"Windows' Linux Subsystem" might have been better as well (WLS), using it as a posessive statement, or "Windows' Subsystem of/with Linux" which would keep the same WSL abbreviation.

Re:DOS Subsystem for Linux by teslalang on Tuesday September 22, 2020 @02:52PM (#24558379)
Perhaps the confused commenters should read the post before commenting. Crazy as that sounds.
Re:DOS Subsystem for Linux by Emendo on Tuesday September 22, 2020 @02:02PM (#24557807)
It makes sense as "A windows subsystem for Linux". Unfortunately, dropping the "A" makes it ambigious.
Re:DOS Subsystem for Linux by rcoveson on Tuesday September 22, 2020 @01:15PM (#24557192)
They're both phrased unnaturally, IMO.

The suffix "for Linux" strongly implies it's software for use on Linux. It's like the "4j" and "4win" suffixes, implying software built for the Java and Windows environments, respectively.

What's more, Windows or DOS as an adjective of subsystem bind more tightly than "for Linux". So if you were to start dropping parts of the name, you'd drop "for Linux" first. Except you can't, because then it's just the Windows Subsystem.

LSW would have been a much more natural name. In a conversation about Windows subsystems, you could refer to it as the Linux Subsystem. If other operating systems picked up on the idea, they would have their own Linux subsystems, e.g. Linux Subsystem for macOS. If you wanted to check if your OS had anything like it, you could search "is there a Linux subsystem for FreeBSD?" Which might turn up results about the Linux ABI in FreeBSD. Speaking of which, imagine if it had been named the FreeBSD ABI for Linux. What an awful pattern! You can't even repeat the pattern unless both modifiers are proper nouns! Could you have called the VFS Subsystem the "FreeBSD Subsystem for VFS"?

Re:DOS Subsystem for Linux by reaperducer on Tuesday September 22, 2020 @02:08PM (#24557886)
They're both phrased unnaturally, IMO.

This is why we teach sentence diagramming in elementary school.

Maybe the person who came up with "WSL" wasn't a native English-speaker?

Re:DOS Subsystem for Linux by WorldMaker on Tuesday September 22, 2020 @02:29PM (#24558136)
Something that should come up early in sentence diagramming but often isn't explained well enough is that sentence diagrams aren't context free, often can be ambiguous, and depend on the context of the speaker to determine referents. Sentence diagrams in the real world are rarely as easy as elementary school examples.

In this case, the context known to the speaker but often missed when trying to "sentence diagram" WSL involves the part "Windows Subsystem". That referent, to which the original author was quite familiar, is invoked in WSL as a single noun in part of the larger noun phrase, and while you could continue to sentence diagram break "Windows Subsystem" into constituent parts here, it is important to remember it as a single connected "atom" to which "for Linux" modifies in the overall noun phrase of "(Windows Subsystem) for Linux". Given that context/referent, the sentence diagram here is unambiguous to the original team/"speaker". It's the audience with much less familiarity with the referent/context in question that has ambiguity problems in trying to "sentence diagram" the noun phrase.

Re:DOS Subsystem for Linux by Fnoord on Tuesday September 22, 2020 @04:12PM (#24559263)
It follows the same naming convention as SFU (Windows Subsystem for Unix) [1] which was equally confusing.

My belief (!!), back then, was that it was intentionally named confusing. Back when it came around, Microsoft was under scrutiny for monopoly behavior. They didn't want Windows to be compatible with Unix in any way; they wanted the world to run Windows (9x, NT) only. That was my belief/theory, as it is now I don't have anything to back it up as it is though. Your theory might equally be viable.

[1] https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

Re:DOS Subsystem for Linux by zapzupnz on Wednesday September 23, 2020 @12:03AM (#24562832)
It's Microsoft. They came up with Xbox, Xbox 360, Xbox One, Xbox One X, and now Xbox Series X. WSL is a drop in the bucket of stupid naming schemes.
Re:DOS Subsystem for Linux by kelnos on Tuesday September 22, 2020 @04:21PM (#24559387)
I expect it's branding. I'm having trouble coming up with a name that sounds unambiguous while keeping "Windows" as the first word. And I doubt Microsoft's branding people would be happy if "Linux" appeared in the title before "Windows".
Re:DOS Subsystem for Linux by rcoveson on Tuesday September 22, 2020 @04:43PM (#24559659)
It's amusing to imagine a stodgy company like Microsoft naming it something indie like "tux4win".
Re:DOS Subsystem for Linux by wooptoo on Tuesday September 22, 2020 @05:19PM (#24560055)
They completely missed the opportunity to call it LinuxFTW
Re:DOS Subsystem for Linux by zhte415 on Tuesday September 22, 2020 @11:21PM (#24562603)
And then one learns Shakespeare in secondary school where all that 'sensible' diagramming and rigidity jumps out of the window.
Re:DOS Subsystem for Linux by dredmorbius on Tuesday September 22, 2020 @02:39PM (#24558238)
"<X> <services|subsystem> on <Y>" strikes me as unambiguous.
Re:DOS Subsystem for Linux by mattnewton on Tuesday September 22, 2020 @05:35PM (#24560220)
But it might have the problem of branding the product as a “Linux subsystem” and they want to sell it as a “windows subsystem”, that runs Linux code
Re:DOS Subsystem for Linux by jlgaddis on Tuesday September 22, 2020 @04:47PM (#24559697)
The poor naming convention goes back ~20 years or so to (at least) "Windows Services for UNIX" (SFU) [0]. The naming was not intuitive then and it still isn't today.

The "problem" is that these products are not what you automatically assume they are!

To illustrate: SFU provided NFS and NIS servers, a cron daemon, a telnet server, and various CLI "utilities" (i.e., standard "services" provided by "UNIX") running on Windows -- not Windows services that run on UNIX!

Once you know that, the "Windows Services for UNIX" name kinda makes sense and helps to understand what the "Windows Subsystem for Linux" and, now, the "DOS Subsystem for Linux" actually are.

---

[0]: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX

Re:DOS Subsystem for Linux by petercooper on Tuesday September 22, 2020 @01:02PM (#24556992)
I know what it means and what way round it is now due to repetition, but WSL struck me as a weird name and confused me at first.

Usually, saying "for Linux" or "for Windows" about something means there's a thing that is for (or "to run on") Linux or Windows, not that the thing is "of" Linux or to enable the use of Linux. I appreciate there are two ways to look at the semantics, but the one they picked for WSL seems the least common one to me.

Re:DOS Subsystem for Linux by gravitas on Tuesday September 22, 2020 @01:12PM (#24557153)
Grammatically, I read the title and thought "yes! finally a way to run those Dell firmware updaters instead of using FreeDOS boot sticks" and then read the comments to find out it's backwards in nature. The phrase is "bad English" in a colloquial sense.
Re:DOS Subsystem for Linux by ogre_codes on Tuesday September 22, 2020 @02:52PM (#24558377)
Next up is Microsoft's browser: Windows Subsystem for HTML
Re:DOS Subsystem for Linux by Aperocky on Tuesday September 22, 2020 @09:06PM (#24561888)
Have you heard of the HTML5 supercomputer? https://twitter.com/Html5Nikola
Re:DOS Subsystem for Linux by Thorrez on Tuesday September 22, 2020 @11:36PM (#24562674)
If it's an HTML5-based device that runs Windows[1] then it's "HTML5 Subsystem for Windows" going by Microsoft's phrase structure.

[1] https://copy.sh/v86/?profile=windows98

Re:DOS Subsystem for Linux by ogre_codes on Tuesday September 22, 2020 @09:46PM (#24562099)
Maybe he should be in charge of naming at Microsoft, can't do worse
Re:DOS Subsystem for Linux by kevinmgranger on Tuesday September 22, 2020 @01:01PM (#24556977)
It's because the WSL name is also confusing.
Re:DOS Subsystem for Linux by mattnewton on Tuesday September 22, 2020 @05:25PM (#24560126)
It’s because the WSL is confusing and doesn’t follow english naming conventions. “X subsystem for y” reads left to right as X is an adjective describing the subsystem, and for seems to indicate y is the platform that X subsystem is for.

Instead it’s seemingly meant to be parsed inside-out with “subsystem for Linux” as one noun indicating a subsystem that runs Linux apps, and DOS as an adjective describing that noun. Maybe wsl did it to keep the windows brand first? Are there many other “windows subsystems for Y” out there and this is a Microsoft-universe term? I don’t know but it’s very strange.

Re:DOS Subsystem for Linux by freedomben on Tuesday September 22, 2020 @12:57PM (#24556924)
Indeed, this confused me as a Linux user who hasn't used Windows in over a decade (and therefore is unfamiliar with the terminology). Thank you. I was reading this as a potential DOS Box alternative to run on Fedora.

If the project maintainer is reading, it would be super helpful to put that at the top of your REMADME.md. I'll even send you a PR. FTR it's not your fault the terminology is confusing :-)

Re:DOS Subsystem for Linux by shmerl on Tuesday September 22, 2020 @01:15PM (#24557194)
Why not compare it with Wine instead?

Besides, latest WSL is not like that anymore, it's a hypervisor running a VM now.

Re:DOS Subsystem for Linux by shmerl on Tuesday September 22, 2020 @03:14PM (#24558598)
It says "DOS subsystem for Linux". The way I'm reading it:

1. It's for Linux (so Linux is the host).

2. It creates some subsystem that runs DOS (either emulated, virtualized or translated like Wine is doing for Windows on Linux).

That can allow running DOS games on Linux for example, instead of using DOSbox for it.

Re:DOS Subsystem for Linux by jjgreen on Wednesday September 23, 2020 @04:11AM (#24564335)
"WSL" is Windows Subsystem for Linux is obviously from the old Services for Unix used to bait-and-switch people to NT, and the grammar in the latter is irrelevant, the meaning of "SFU" is clear.
Re:DOS Subsystem for Linux by dboreham on Wednesday September 23, 2020 @01:10AM (#24563204)
The misunderstanding comes from choosing a name for it that stongly implies it is not the thing that it is.
Re:DOS Subsystem for Linux by antihero on Tuesday September 22, 2020 @03:27PM (#24558733)
Would prefer me some LSD to be honest.
Re:DOS Subsystem for Linux by m463 on Tuesday September 22, 2020 @07:13PM (#24561111)
Maybe it's wishful thinking that the embracing and extending can be recursively embraced. :)
Re:DOS Subsystem for Linux by em-bee on Tuesday September 22, 2020 @01:59PM (#24557769)
i think the confusion comes from the phrase "for those who prefer a DOS environment".

maybe it could be phrased as "for those who want linux but need to run DOS as their main OS"

Re:DOS Subsystem for Linux by xpressvideoz on Tuesday September 22, 2020 @12:55PM (#24556898)
Yeah, I got that too. It was clear that the name was a parody of WSL.
Re:DOS Subsystem for Linux by tus88 on Tuesday September 22, 2020 @03:30PM (#24558778)
Wuts WSL?
Re:DOS Subsystem for Linux by gabereiser on Tuesday September 22, 2020 @01:58PM (#24557745)
I've been fielding these questions all day. Saying the same thing. It's for "DOS" so you can run _bash_. Ok? People got all excited for Prince of Persia... smh. +1