From be49aa7ddec52e121d562e14d4d93fd301b05fbb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 4 Nov 2011 19:19:35 +0100 Subject: IRC. --- open_issues/bsd_compatibility.mdwn | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 open_issues/bsd_compatibility.mdwn (limited to 'open_issues/bsd_compatibility.mdwn') diff --git a/open_issues/bsd_compatibility.mdwn b/open_issues/bsd_compatibility.mdwn new file mode 100644 index 00000000..5c916908 --- /dev/null +++ b/open_issues/bsd_compatibility.mdwn @@ -0,0 +1,34 @@ +[[!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: + + hm, why our sys/param.h #define's BSD? + pinotree: because we're evil + is that correct? + (the define, not the evilness) + 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) + braunr: but mach being bsd-ish won't make the userland (glibc) + interfaces bsd-ish, will it? + pinotree: no + braunr: so...? :) + pinotree: i guesse there are bsdisms in the glibc hurd specific + code, possibly because of mach + or they used to be bsdisms, before being standardized + e.g. mmap + braunr: hrmm... + braunr: the BSDisms are there on purpose... Hurd was originally + even meant to be binary-compatible with BSD + nothing to do with Mach really + antrik: ok -- cgit v1.2.3