summaryrefslogtreecommitdiff
path: root/faq/posix_compatibility.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-12-22 08:22:59 +0100
committerThomas Schwinge <thomas@schwinge.name>2010-12-22 08:22:59 +0100
commita6713e05645d07e9c38717fc09c8e3b50842e524 (patch)
tree8859a7933f084e8046bd26c45510143add0e65ab /faq/posix_compatibility.mdwn
parentbd0ffbcc4e0f7abf5e811850fb9ebd93ca649966 (diff)
faq/posix_compatibility: Comments by Olaf.
Diffstat (limited to 'faq/posix_compatibility.mdwn')
-rw-r--r--faq/posix_compatibility.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/faq/posix_compatibility.mdwn b/faq/posix_compatibility.mdwn
index 1525a7ad..a54822c5 100644
--- a/faq/posix_compatibility.mdwn
+++ b/faq/posix_compatibility.mdwn
@@ -30,3 +30,20 @@ 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.
+
+
+\#hurd IRC channel on Freenode, 2010-12-21:
+
+ <antrik> tschwinge: the writeup ignores the fact that POSIX compatibility
+ is not only for applications, but also for users familiar with the UNIX
+ environment
+ <antrik> also, I still don't buy the fact that most software is not written
+ for POSIX. even if assuming that GNOME programs don't use POSIX (which is
+ only half true), there is a lot of other software in a system that is
+ just as important, though less visible
+ <antrik> (server software, startup system, device management, automation,
+ ...)
+ <antrik> tschwinge: BTW, I meant to (and partially did) write a blog
+ article on this topic -- but I didn't get around to finish it...
+
+[[!tag open_issue_documentation]]