diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2019-03-23 00:16:23 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2019-03-23 00:16:23 +0100 |
| commit | 06c5a833c0aabe7131be173a334957e8013d029f (patch) | |
| tree | 1c2bf6be8cbc03f73736e53e69280ce90c9b90fe /faq | |
| parent | d1d618ab4d4f5914623e8f8cd791b7c69c9b3334 (diff) | |
| parent | 7985a706686a6a564b379014ac4c7c0006f715e5 (diff) | |
Merge branch 'master' of braunbox:~hurd-web/hurd-web
Diffstat (limited to 'faq')
| -rw-r--r-- | faq/posix_compatibility.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/faq/posix_compatibility.mdwn b/faq/posix_compatibility.mdwn index 2212a7d4..db7989a6 100644 --- a/faq/posix_compatibility.mdwn +++ b/faq/posix_compatibility.mdwn @@ -13,6 +13,8 @@ License|/fdl]]."]]"""]] [[!meta title="POSIX compatibility"]] +Many computer operating systems strive to be POSIX (Portable Operating System Interface) compliant, as it makes cross-compiling and program portability much easier than having to package something for every new distribution. + Is it favorable of rather a hindrance to be compatible to POSIX and similar standards? @@ -33,3 +35,7 @@ striving for total POSIX compliance -- and the high-level programs (that is, their users) may not even notice this, but we would avoid a lot of overhead that comes with wrapping the [[Hurd interfaces|hurd/interface]] to be POSIX compliant. + +# External +* The Open Groups [POSIX Specification](https://pubs.opengroup.org/onlinepubs/9699919799/) +* Wikipedia [article on POSIX](https://en.wikipedia.org/wiki/POSIX) |