*BSD News Article 37792


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!news.cac.psu.edu!news.pop.psu.edu!ra.nrl.navy.mil!cs.umd.edu!newsfeed.gsfc.nasa.gov!news!kstailey
From: kstailey@leidecker.gsfc.nasa.gov (Kenneth Stailey)
Newsgroups: comp.os.386bsd.misc
Subject: Re: The Real reasons the *BSDs should cooperate, if not merge.
Date: 12 Nov 1994 17:24:09 GMT
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Lines: 13
Message-ID: <KSTAILEY.94Nov12122409@leidecker.gsfc.nasa.gov>
References: <38s02r$gp7@nntp1.u.washington.edu> <CyF7HK.5BF@indirect.com>
	<KSTAILEY.94Nov5164528@leidecker.gsfc.nasa.gov> <CytGL4.1B3@deshaw.com>
NNTP-Posting-Host: leidecker.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In-reply-to: christos@deshaw.com's message of Sat, 5 Nov 1994 22:46:16 GMT

>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]

So if a commerical vendor wants to release a single binary for
NetBSD/386i, FreeBSD, 386BSD, SCO, LINUX?, etc. he/she can do it as a
static iBCS2 COFF binary?

Ken