summaryrefslogtreecommitdiff
path: root/faq
diff options
context:
space:
mode:
authorMutoShack <MutoShack@web>2019-03-22 03:49:35 +0100
committerGNU Hurd web pages engine <web-hurd@gnu.org>2019-03-22 03:49:35 +0100
commit91820020e22b20167f5bfb1adbbb31af5b7bbeb3 (patch)
treebe56225a428e45da8949d3ef526fd1c16bafaf8b /faq
parentc75b9886d011785857252180b61a91580be7ea8a (diff)
Add external links & define acronym
Diffstat (limited to 'faq')
-rw-r--r--faq/posix_compatibility.mdwn6
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)