From owner-freebsd-questions Fri Sep 13 18:20:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04030 for questions-outgoing; Fri, 13 Sep 1996 18:20:58 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts12-line4.uoregon.edu [128.223.150.136]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04025 for ; Fri, 13 Sep 1996 18:20:53 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id SAA00297; Fri, 13 Sep 1996 18:21:03 -0700 (PDT) Date: Fri, 13 Sep 1996 18:21:03 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: GreggD@caddmicro.com cc: freebsd-questions@freebsd.org Subject: Re: Booting from sd1 at BIOS Drive 0 In-Reply-To: <9608128425.AA842546892@caddmic.CADDMICRO.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 12 Sep 1996 GreggD@caddmicro.com wrote: > I have a 2GB Seagate Barracuda at ID1 (FreeBSD 2.2 960801-SNAP) > When installing, the Barracuda was the BIOS 0 bootable drive, and > sysinstall put a bootblock on this device correctly...sort of.... > The only problem is, if I neglect to type "0:sd(1,a)/kernel" at the > "Boot:" prompt, the system understandably panics when trying to mount > / on sd(0,a). Try rebuilding your kernel and modifying the 'kernel' line to read something like: kernel root on sd1 ..... Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major