3 ms·
But it's not just GNU running on top of the Windows kernel. It's GNU executables which think they're communicating with a Linux kernel. I understand being frust
by dikaiosune 11y ago
But it's not just GNU running on top of the Windows kernel. It's GNU executables which think they're communicating with a Linux kernel. I understand being frustrated about the already-forming naming conventions (although they've been chanting GNU/Linux forever and it still isn't used in common parlance), but GNU/kWindows doesn't capture the nature of the system either.
- anonymfus 11y agoGNU/WSL
- ecma 11y agoAccurate. Technically the Microsoft compatibility later could have been entirely done at the library level by replicating POSIX and adding an ELF linker/loader. There would have been some edge cases around Linux specific source but the GNU core would have been well served by something like that. The reason the language is all centered around Linux is because what they chose to do was do a Linux syscall compatibility layer. Really it could be called GNU/sLinux/kWindows but nobody is ever going to bother with that mouthful. Edit: I should add that this doesn't mean I agree with the use of Linux here - I just understand why that's the case. I would much prefer if those involved went to the trouble of explaining what GNU is to those consumers who are interested. Pretty unlikely Microsoft would be leading that given GNU's position on Windows.
- ryao 11y agoCygwin does that. forking does not perform very well.