From 91820020e22b20167f5bfb1adbbb31af5b7bbeb3 Mon Sep 17 00:00:00 2001 From: MutoShack Date: Fri, 22 Mar 2019 03:49:35 +0100 Subject: Add external links & define acronym --- faq/posix_compatibility.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'faq/posix_compatibility.mdwn') 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) -- cgit v1.2.3