summaryrefslogtreecommitdiff
path: root/faq/posix_compatibility.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/posix_compatibility.mdwn')
-rw-r--r--faq/posix_compatibility.mdwn19
1 files changed, 1 insertions, 18 deletions
diff --git a/faq/posix_compatibility.mdwn b/faq/posix_compatibility.mdwn
index a54822c5..4490b7cb 100644
--- a/faq/posix_compatibility.mdwn
+++ b/faq/posix_compatibility.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -30,20 +30,3 @@ 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]]