Why are most Linux distributions not POSIX-compliant? I've seen in lots of places that they're not (e.g. Mostly POSIX-compliant) but there's been no real explanation to back this up.
Is there something the C library and/or tools could do to get around this (i.e. no modifications to the kernel itself)? What needs to be done?
The supposed duplicate is asking which Linux distribution is POSIX-compliant; this is asking why most Linux distributions aren't POSIX-compliant. I'm asking for specific details (i.e. some function or command isn't compliant), not the reasons the specific distributions don't (try to) get certified.
This comment from @PhilipCouling (thanks!) explains it well:
Compliance and certification are different subjects. The answers point to cost of (re)certification which is irrelevant to the subject of (non)compliance.
/bin/cd
, which will not have any effect when called, one might question why any particular distribution will strive to meet compliance standards. – doneal24 Dec 06 '19 at 18:15/bin/cd
, but it's used to test if you can change directories into a path without actually changing directories. It's probably meant to be used in other tasks, like shell scripting and writingMakefile
s. – S.S. Anne Dec 06 '19 at 21:27