Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!usc!elroy.jpl.nasa.gov!ames!skates.gsfc.nasa.gov!nasahq!lupine.nsi.nasa.gov!mnewell Newsgroups: comp.os.386bsd.questions Subject: Re: To NetBSD or Not NetBSD Message-ID: <1993Jun15.120920.449@nhqvax.hq.nasa.gov> From: mnewell@lupine.nsi.nasa.gov. (Mike Newell) Date: 15 Jun 93 12:09:19 +0600 Reply-To: mnewell@lupine.nsi.nasa.gov. References: <CGD.93Jun15030102@erewhon.CS.Berkeley.EDU> Distribution: world Organization: Sun Microsystems Nntp-Posting-Host: lupine.nsi.nasa.gov Lines: 41 In article 93Jun15030102@erewhon.CS.Berkeley.EDU, cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou) writes: >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... > That may be true. But the version I got (from sunlamp) was missing a header file (I'm sorry to say I can't remember which one...) And the "compile" directory wasn't created. >=> [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... > Ok. Perhaps I got a flaky distribution. I did have to split it up into tiny files to transmit it, since I was downloading it via SLIP on my 386bsd system and the line wouldn't stay up for the whole download. I didn't report it because I never got the system to the point where I felt it was usable; I got sufficiently frustrated to drop it for the time being and wait until something more stable came along. None the less, /bin/sh kept core dumping. At least, commands termintated and the file "core.sh" kept appearing at random intervals. Mike Newell NASA Advanced Network Applications [BTW - I received a possible explanation of why the busmouse driver wouldn't work via Email. Unfortunately the sender's Email address wasn't replyable from my host. Thanks!!!!]