Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA5195 ; Tue, 22 Dec 92 09:01:16 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!jwp20406 From: jwp20406@uxa.cso.uiuc.edu (Jeffrey Palmer) Subject: An interesting problem (and solution?) Message-ID: <BzHwLG.Dn0@news.cso.uiuc.edu> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Organization: University of Illinois at Urbana Date: Sat, 19 Dec 1992 07:24:50 GMT Lines: 46 Hey all, I love 386bsd, but lately I have been having some very strange problems... I was just windering if anyone else out there might have an idea as to why in the world my system would be doing this... The problem first started when I attempted to install a second Western Digital 2200a 200 Meg drive in my 486-50 Gateway 2000 (which I've had no problems with, in relation to 386bsd). I found out quickly that I needed patches, so patch away I did... I tried the barsoom patches, but they didn't work. It seemed that they would see only the initial drive on my controller, and instead of a second drive, all I saw was another image of the first. Well, needless to say, that didn't do me any good. I installed the other 2nd hard-drive patches from the unofficial directory at agate, and they worked like a charm. However, although I could now label and newfs my drive, whenever I tried to mount or access the drive at startup, the label seemed to have a habit of either disappearing or causing the mmachine to hang while loading. Well, since I just finished finals I decided to dig around in 'ufs_disksubr.c' I wanted to find out where exactly my machine was crashing. Now I know this sounds like a bogus way to go about this, but I don't know too much about kernel debugging, so I put in some printf statements inbetween some lines that I thought looked interesting. Well, after a while I realized that this new kernel was n of the paritition to boot from but, more importantly for this discussion, allows booting from paritions on other drives. OS-BS is not one of them (the author considered it but there was no more code space left). I vaguely remember another one called "bootp" or something that I think did support this. This should allow the 386BSD primary and secondary boots to be on another disk. There was a thread on this about a month or so ago when someone was trying to do just this (then again, this might have been one of you ;-)). I never read a posting on whether it was successful or not. I seem to have one of the postings. In "booting-up "386bsd" from the 2nd-Hard-Drive", nemossan@uitec.ac.jp talks about using a boot progra