From owner-freebsd-current Thu Dec 3 02:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24548 for freebsd-current-outgoing; Thu, 3 Dec 1998 02:13:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-27-dbn.dial-up.net [196.34.155.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24540 for ; Thu, 3 Dec 1998 02:13:05 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA14987; Thu, 3 Dec 1998 11:58:15 +0200 (SAT) From: Robert Nordier Message-Id: <199812030958.LAA14987@ceia.nordier.com> Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-Reply-To: <10151.912646644@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 2, 98 04:57:24 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 3 Dec 1998 11:58:13 +0200 (SAT) Cc: john.saunders@scitec.com.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > What I did...Booted from the CD and selected slice 2 (which > > was empty) to install to. Using the disk label editor I created > > Which won't work. The FreeBSD boot loader, at least last I checked, > is too stupid to know that there might be more than one FreeBSD slice > on the disk and it just stops at the first one it finds. If you want > to run different versions of FreeBSD on the same box, they at least > need to reside on physically different drives. This is correct for the old (/sys/i386/boot/biosboot) boot blocks. However, the new (/sys/boot/i386/boot2) boot blocks specifically provide for booting from any slice. You can have four FreeBSD slices per disk, and pressing F4 will boot from slice 4, not from slice 1. The new boot blocks also allow you to override the slice using the extended syntax wd(0,2,a) where "2" means slice 2, though this is presently undocumented. The new boot blocks attempt to pass control to "/boot/loader" by default; but this can be overridden by specifying "/kernel" in /boot.config. They will also revert to loading "/kernel" if "/boot/loader" isn't found. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message