summaryrefslogtreecommitdiff
path: root/open_issues/bsd_compatibility.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/bsd_compatibility.mdwn')
-rw-r--r--open_issues/bsd_compatibility.mdwn34
1 files changed, 0 insertions, 34 deletions
diff --git a/open_issues/bsd_compatibility.mdwn b/open_issues/bsd_compatibility.mdwn
deleted file mode 100644
index 5c916908..00000000
--- a/open_issues/bsd_compatibility.mdwn
+++ /dev/null
@@ -1,34 +0,0 @@
-[[!meta copyright="Copyright © 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
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!tag open_issue_documentation]]
-
-IRC, freenode, #hurd, 2011-10-12:
-
- <pinotree> hm, why our sys/param.h #define's BSD?
- <braunr> pinotree: because we're evil
- <pinotree> is that correct?
- <pinotree> (the define, not the evilness)
- <braunr> pinotree: i think it's because the Hurd is closer to the BSD
- interfaces, probably because of Mach (which is itself derived from
- BSD4.2)
- <pinotree> braunr: but mach being bsd-ish won't make the userland (glibc)
- interfaces bsd-ish, will it?
- <braunr> pinotree: no
- <pinotree> braunr: so...? :)
- <braunr> pinotree: i guesse there are bsdisms in the glibc hurd specific
- code, possibly because of mach
- <braunr> or they used to be bsdisms, before being standardized
- <braunr> e.g. mmap
- <pinotree> braunr: hrmm...
- <antrik> braunr: the BSDisms are there on purpose... Hurd was originally
- even meant to be binary-compatible with BSD
- <antrik> nothing to do with Mach really
- <braunr> antrik: ok