Re:How many products does Microsoft have named 'Copilot'? I ...
by rusk on Sunday April 05, 2026 @06:50AM
(#47648106)
It needs an apostrophe then it makes more sense “Windows’ Subsystem for Linux”
It is a Windows Subsystem, that caters to running Linux.
It’s a functional title not an architectural one.
Re:How many products does Microsoft have named 'Copilot'? I ...
by Jenk on Sunday April 05, 2026 @06:57AM
(#47648139)
Or a colon:
Windows Subsystem for: Linux
Re:How many products does Microsoft have named 'Copilot'? I ...
by 1718627440 on Tuesday April 07, 2026 @07:32AM
(#47673570)
Subsystem isn't used as a random English word here, "Windows Subsystem" is already a fixed term. So you wouldn't introduce a possessive relation into the term when using it.
Re:How many products does Microsoft have named 'Copilot'? I ...
by rusk on Monday April 13, 2026 @02:33AM
(#47748398)
Indeed, I was trying to make it easier for you.
Re:How many products does Microsoft have named 'Copilot'? I ...
by lxgr on Sunday April 05, 2026 @07:07AM
(#47648188)
That doesn't seem like a contradiction to the idea that "Windows subsystem" is (at least after WSL 1 and especially 2) a description for a functionality (i.e. running binaries targeting a different OS's interfaces), not an implementation.
Re:How many products does Microsoft have named 'Copilot'? I ...
by dataflow on Sunday April 05, 2026 @10:58AM
(#47650108)
No, as I explained, that's not what the actual subsystem architecture did. The binaries very much targeted Windows and did not target any other OSes. They weren't (say) ELF files targeting Linux, they were PE files targeting Windows, and you had to compile them from source with special flags to target those subsystems on Windows. You could not run those binaries on other OSes. The compatibility was at the source level, not at the binary level.
If you want a list of actual subsystems Windows recognizes, this should be pretty accurate:
https://learn.microsoft.com/en-us/windows/win32/debug/pe-for...
The real reason for calling it a subsystem was almost entirely for familiarity with the previous attempts at running Linux programs, which were based on that subsystem feature (the POSIX subsystem and the Subsystem for UNIX-based Applications).