3 ms·
I see that Linux and MacOS run Unix dervied kernels. I dont see how Windows does so. Its heritage is more along the line of VMS. https://www.itprotoday.com/co
by ThinkBeat 8y ago
I see that Linux and MacOS run Unix dervied kernels.
I dont see how Windows does so. Its heritage is more
along the line of VMS.
https://www.itprotoday.com/compute-engines/windows-nt-and-vms-rest-story https://www.itprotoday.com/compute-engines/windows-nt-and-vm...
Unless he means the Windows Subsystem for Linux but it is
my understanding that it is not runing a Linux kernel, but
mapping to the Windows (NT) kernel.
- ulkesh 8y agoI suspect he means the WSL given the context of the previous sentence.
- ThinkBeat 8y agoWSL provides a Linux-compatible kernel interface developed by Microsoft (containing no Linux kernel code) https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
- ytwj 8y agoDidn't windows used to distribute BSD code? The old EULAs used to mention the regents of berkley. Was that the Windows kernel or some network stack?
- m-i-l 8y agoYes, the Windows TCP/IP stack was from BSD. I'm not sure if the code is still in Windows, but I think it is still configured via an etc/hosts file. I believe the BSD licence was preferable to Microsoft (as it was to Apple who based OSX on BSD). The networking stack was supposedly better on BSD than Linux too, but I'm not sure how correct that is (but I did hear that the software company I set up a website for in the mid 1990s switched from Linux to NetBSD pretty much as soon as I left for that reason).
- mnbvkhgvmj 8y agoytwj your comment has been killed for some reason and I don't have enough karma to vouch it. There was some BSD code for the network stack in Windows 95. This was all legal and license compatible. I'm pretty sure it was gone by the next windows version.