Hacker News Reader

I can easily relate to this, started with Xenix, moved into DG-UX at university, we moved into GNU/Linux after that server eventually died, so it was mostly used of OS related classes.

At work GNU/Linux was just an internal server, all real work was being done in Solaris, HP-UX and Aix servers.

So fast forward to modern times and even Microsoft uses Linux kernel syscalls on their new POSIX personality subsystem, instead of actually supporting POSIX.

View on HN

> instead of actually supporting POSIX

POSIX support is in the API, not the syscalls. musl libc places great emphasis on POSIX conformance. So if you ran a musl-based distro atop WSL, that should give you what you want, or at least something closer.

Currently only Ubuntu, OpenSUSE and SLES are supported. None of them is muslc based, right?

Doesn't matter, the stable interface in Linux is the syscalls, not the libc. Same goes for WSL.

Syscalls are not POSIX APIs.

POSIX and Linux are generally believed to be different entities.

Which is why I keep stressing POSIX.

> instead of actually supporting POSIX

What do you mean? Using Linux kernel syscalls is just one of many ways to "actually support POSIX".

Syscalls are not POSIX APIs.

Do you know that by default GNU tools don't respect all POSIX expected behaviours and it needs to be explictly enabled?

Reply on news.ycombinator.com