Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!hplabs!ucbvax!pasteur.berkeley.edu!cgd
From: cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.questions
Subject: Re: To NetBSD or Not NetBSD
Message-ID: <CGD.93Jun15030102@erewhon.CS.Berkeley.EDU>
Date: 15 Jun 93 10:01:02 GMT
References: <1993Jun11.084954.2099@yvax.byu.edu> <1993Jun14.195650.444@nhqvax.hq.nasa.gov>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: Kernel Hackers 'r' Us
Lines: 34
In-reply-to: mnewell@lupine.nsi.nasa.gov.'s message of 14 Jun 93 19:56:49 +0600
In article <1993Jun14.195650.444@nhqvax.hq.nasa.gov> mnewell@lupine.nsi.nasa.gov. (Mike Newell) writes:
=> [3] To install the bus mouse I had to rebuild the kernel. To do that I
=> had to install the source kit. Unfortunately the source kit didn't
=> come with all the ".h" files I needed [I got them from 386bsd] and
=> the installation procedure didn't create the "compile" directory.
i think you're comfused about something or other:
the ksrc08 distribution set *definitely* comes with all of
the include files necessary to build a kernel; it's basically
a straight-off tar of /sys...
=> [4] The "/bin/sh" shell kept doing core dumps. They appeared random;
=> script that ran fine once would dump a couple of times and then run
=> fine again after a couple of tries.
sh dumping core has not ever been reported to us...
as for any personality conflicts:
it's worth noting that the NetBSD group is in almost-constant
contact with the patchkit and 386bsd interim release groups...
not only do we trade code, but, e.g. NetBSD often plays
"guinea pig" for new patches...
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass