summaryrefslogtreecommitdiff
path: root/service_solahart_jakarta_selatan__082122541663/bsd_compatibility.mdwn
blob: 5c916908077414c684db6fad3a4a0dfcef445713 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
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:

    <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