*BSD News Article 26679


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!envoy.wl.com!caen!batcomputer!cornell!rochester!udel!news.sprintlink.net!news.clark.net!news.clark.net!not-for-mail
From: ack@clark.net (Eric S. Hvozda)
Newsgroups: comp.os.386bsd.questions
Subject: Re: default boot off hd(1,a)386bsd?
Date: 28 Jan 1994 15:27:14 -0500
Organization: Clark Internet Services, Inc.
Lines: 48
Message-ID: <2ibsf2$r91@explorer.clark.net>
References: <clary.759753970@s1.elec.uq.oz.au>
NNTP-Posting-Host: explorer.clark.net
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Keywords: bteasy

In article <clary.759753970@s1.elec.uq.oz.au>,
Clary Harridge <clary@s1.elec.uq.oz.au> wrote:
>
>My configuration is
>	Drive 0	DOS on ESDI drive
>	Drive 1 UNIX on SCSI drive, No DOS partition.
>
>[...]
>
>However I need to type "hd(1,a)386bsd" each time I bring up unix.
>So I want to modify the Unix bootstrap to make this the default
>rather than "wd(0,a)386bsd".
>
>[...]
>
>	cd /usr/mdec
>	disklabel -w -r sd0a Seagate_ST3390N sdboot bootsd
>
>I now reinstall bteasy on drive 1 and can no longer boot drive 1.

Well this covered in the FAQ, and I'm a NetBSD user, but I have two IDE
drives, so I kinda know what to do.  If FreeBSD is different, someone who
knows better please correct my mis-information...

First, you *will* have to change boot.c as per the info in the FAQ.  But you
need an additional change.  This change will probaly be to the variable
called maj.  At any rate, you need to tell the boot blocks to look at hd(1,a)
instead of wd(0,a), right?  So you need to change the maj device as well as 
the unit.

Then you need to recompile the boot blocks.  When you install them, they need
to be on the *boot* device, not the device you want to boot from.  For you
this would be wd0, not sd0.  So by going by what you did above, you labeled
the SCSI disk, not the ESDI.  The ESDI is your boot device by what you
said above, right? (you said disk 0 is the ESDI and BIOS only knows how to
boot from disk 0)  To label wd0, you will need to have at least a 1 cyl *BSD
partition on wd0.

Outta question, why are you using BootEasy?  OS-BS is nice IMHO and unless 
FreeBSD is different from NetBSD, you cannot boot *BSD from the second drive 
like that at this time.  You need to have boot blocks on the bootable device 
no matter what.  You can point those blocks anywhere you want to.

BTW, anyone know why boot blocks specify hd when you are using a sd device?
Why not just make it uniform like the wd devices?
-- 
Ack!
Creek, not creek; Pop not soda; Car needs washed...