Return to BSD News archive
Newsgroups: comp.os.386bsd.misc
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!usc!math.ohio-state.edu!deshaw.com!christos
From: christos@deshaw.com (Christos Zoulas)
Subject: Re: The Real reasons the *BSDs should cooperate, if not merge.
Message-ID: <CytGL4.1B3@deshaw.com>
Sender: usenet@deshaw.com
Nntp-Posting-Host: cs4
Organization: D. E. Shaw & Co.
References: <38s02r$gp7@nntp1.u.washington.edu> <CyF7HK.5BF@indirect.com> <KSTAILEY.94Nov5164528@leidecker.gsfc.nasa.gov>
Date: Sat, 5 Nov 1994 22:46:16 GMT
Lines: 25
In article <KSTAILEY.94Nov5164528@leidecker.gsfc.nasa.gov> kstailey@leidecker.gsfc.nasa.gov (Kenneth Stailey) writes:
>
>What is iBCS2? NetBSD has a kernel option COMPAT_IBCS2 as well as a
>suboption COMPAT_SVR4. The FAQ has nothing in its table of contents
>and only a blurb about "working on COFF and ELF compatiblity" in some
>*BSD vs LINUX section.
>
Well, COMPAT_IBCS2 == IBCS2/COFF
COMPAT_SVR4 == IBCS2/ELF
Yes, there is lots of code that is duplicated and should be shared.
Yes, the names are confusing and should be changed.
But:
From what I heard:
COMPAT_IBCS2 is almost complete and runs many commercial binaries.
From what I know:
COMPAT_SVR4 should run many dynamically linked binaries, except ones that
use the network, or depend on ioctl's doing something :-)
[this stuff is not in the NetBSD-1.0 tree]
christos