Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:4949 comp.os.386bsd.misc:932 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: from 386bsd0.1 to FreeBSD or NetBSD 0.9 Message-ID: <CD3zDn.7qK@veda.is> Date: 9 Sep 93 22:48:44 GMT References: <1993Sep8.231610.9740@ccds3.ntu.edu.tw>, <CD190K.FwG@latcs1.lat.oz.au> <CD3JII.F5w.1@cs.cmu.edu> Organization: Veda Systems, Iceland Lines: 22 rvb+@cs.cmu.edu (Robert Baron) writes: >So this was working fine with 0.1+0.2.3. I cut over to FreeBSD there >and I got as far as trashing my disk, but I can not get FreeBSD to >successfully come up. On the other hand, NetBsd does not even see >the wd drives, so I lose there too. And sadly, I now have nothing. I would suggest for now, install FreeBSD with a pk0.2.[34] kernel, the old kernel should boot correctly in the new environment. Then rename any driver sources that don't work in the FreeBSD tree, and put pk0.2.[34] sources in their place. The scsi driver is everything in /sys/scsi and whichever low-level scsi driver that you are using in /sys/i386/isa, The wd driver is probably only /sys/i386/isa/wd.c Once you have compiled the new kernel you will be using a FreeBSD system except for whatever old driver you had to use. Then you are pretty much sorted out. I am running a FreeBSD system with pk0.2.4 scsi drivers, because my disks are not recognised by the new scsi code. It's nonetheless FreeBSD. -- adam@veda.is