From owner-freebsd-hackers Tue Aug 3 9: 9:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91]) by hub.freebsd.org (Postfix) with SMTP id C908B152D4 for ; Tue, 3 Aug 1999 09:09:26 -0700 (PDT) (envelope-from cillian@baker.ie) Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP; Tue, 3 Aug 1999 17:12:58 +0100 Message-ID: <37A710CA.EE6281B3@baker.ie> Date: Tue, 03 Aug 1999 16:54:50 +0100 From: Cillian Sharkey X-Mailer: Mozilla 4.6 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Graham Wheeler Cc: Graham Wheeler , hackers@freebsd.org Subject: Re: Multiple versions of FreeBSD on one HDD References: <37A6CDCF.FBFEFC1F@baker.ie> <37A6F353.C449445E@cdsec.com> <37A6F31E.E9F6F912@cdsec.com> <37A70D9C.B7D88F53@cdsec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you do have the installations in two seperate slices on the one disk, > > you should be able to use a boot selector to boot which ever slice you > > want. > > Boot selector programs like os-bs work with partitions, not disk slices. > That's why I wanted separate partitions. At the moment I have os-bs > installed but it will only get me as far as a BSD boot. I then have to > quickly hit a key and enter: > > 0:wd(0,c)/kernel > > to boot 2.2.8 (3.2 will boot by default). Ah yes, I see the problem now. Even if you have two seperate slices say wd0s1 and wd0s2 and boot into your selected one via os-bs, the boot prompt on either will always be 0:wd(0,a)/kernel ..and wd0a always points to the first BSD slice found on the disk. (in this case wd0s1 which is either 2.2.8 or 3.2 depending on where you installed them). I think the FreeBSD boot loader might need the option of specifying which *slice* to boot from rather than just which disk (0,1,2 etc.) and partition (a,b,c,d etc.) for the moment I think you'll just have to type in the line above every time you need to boot into 2.2.8 (or get another HD but that was the problem we've been trying to solve :) Anybody else out there have suggestions ? - Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message