*BSD News Article 2675


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!caen!uunet!wupost!gumby!yale!mintaka.lcs.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!eichin
From: eichin@athena.mit.edu (Mark W. Eichin)
Newsgroups: comp.unix.bsd
Subject: 0.1, incrementally...
Message-ID: <EICHIN.92Jul28222049@tsx-11.mit.edu>
Date: 29 Jul 92 02:20:55 GMT
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 18
Nntp-Posting-Host: tsx-11.mit.edu

Since my 0.0 system is actually "on the air" (I can rlogin to it, ftp,
run emacs...) I've been slightly reluctant to "blow everything away"
to upgrade. Since an important reason for me to use 386bsd is to learn
even more about BSD than I already know, I made diffs of the kernels
and read things before trying it out. I built a 0.1 build tree and set
up a sufficient config file (no scsi, no ethernet, no tape, MFS but
not ISOFS, ddb, unofficial/com.cgd) and built a 0.1 kernel on the 0.0
system. It booted, then hung; turns out it needed the 0.1 init, so I
copied that in too... That booted to a (garbled, of course :-) login
prompt. Did some mknod's to fix com1 and com2 for the new driver. ps
-u dies with a floating exception, but we've seen that here before
too. 
	NFS over SLIP still hangs, but now it seems more clearly
related to silo overflow than before, so I've got something to
diagnose now :-)
				_Mark_ <eichin@athena.mit.edu>
				MIT Student Information Processing Board
				Cygnus Support <eichin@cygnus.com>