From owner-freebsd-questions  Fri Oct 11 20:09:20 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA19021
          for questions-outgoing; Fri, 11 Oct 1996 20:09:20 -0700 (PDT)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA19013
          for <questions@freebsd.org>; Fri, 11 Oct 1996 20:09:18 -0700 (PDT)
Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id UAA00483; Fri, 11 Oct 1996 20:09:16 -0700 (PDT)
Date: Fri, 11 Oct 1996 20:09:16 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: dwhite@resnet.uoregon.edu
To: Sean Eric Fagan <sef@kithrup.com>
cc: questions@freebsd.org
Subject: Re: Running freebsd on drive D:
In-Reply-To: <199610111750.KAA09879@kithrup.com>
Message-ID: <Pine.BSI.3.94.961011200810.232P-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Fri, 11 Oct 1996, Sean Eric Fagan wrote:

> In particular, I want it to default to:
> 
> 	1:sd(1,a)kernel
> 
> at the boot prompt; it was defaulting to
> 
> 	1:sd(0,a)kernel
> 
> which is not waht I want!  (I have two scsi drives, obviously.)

Ouch.  This is probably due to some sort of mis-detection on the
bootblock's part and isn't easy to fix :(  Make sure the bootblocks are on
disk 1 and not disk 0.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major