https://marc.info/?l=openbsd-tech&m=161435521906992&w=2
https://github.com/NetBSD/src/commit/6ce3f21
https://github.com/NetBSD/src/commit/1a68594
He also came to the same conclusion compat layers were a dead end (OpenBSD removed all compat_*(8) support, including Linux).
The interesting thing about WSLv1 is the pico process concept, not the syscall compatibility.
But there are plenty of examples of compatibility layers like this throughout computing history. WINE, cygwin, Linux compat, etc.
Microsoft even went down this road already in the 80s with Xenix before abandoning the idea of Unix.
The only novel part of WSL was the marketing folks
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
Then with the release of XP it was replaced with: https://en.wikipedia.org/wiki/Windows_Services_for_UNIX
Admittedly back then I was working for a place that mainly developed in Perl, so I didn’t port a whole lot of ELFs across. So maybe I’m misremembering
Thanks for correction
It was nice because getting anything approved by the windows sysadmin group was like changing the tire on a moving truck.
It was more than a godsend, because when a windows server was plugging into "the wrong vlan" we could just give them the tcpdump command to capture a CDP/LLDP packet and tell us which switch and port the box was physically connected to.
For example with tcpdump:
https://github.com/search?q=repo%3Athe-tcpdump-group%2Ftcpdu...
So it’s not quite the same thing as what we were discussing further up the thread. Though it’s still an interesting anecdote in its own right.
Both FreeBSD and Illumos were running Linux applications (at various levels of compatibility) many years prior to wsl v1. Joyent even went as far as re-implementing the Docker api to allow running OCI images natively in LX zones. Hence, it wasn't even that novel of an idea.