From owner-freebsd-questions Tue May 27 23:35:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27891 for questions-outgoing; Tue, 27 May 1997 23:35:42 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA27885 for ; Tue, 27 May 1997 23:35:37 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA15172; Wed, 28 May 1997 09:34:30 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma015164; Wed May 28 09:34:02 1997 Message-ID: <338BD1C1.78DE@barcode.co.il> Date: Wed, 28 May 1997 09:33:37 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: chaos@tgci.com CC: questions@FreeBSD.ORG Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't boot from s References: <199705280432.VAA08213@train.tgci.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Riley J. McIntire wrote: > > Hmmm...maybe I'm not clear. I would like to know if one can dual > boot two versions of fbsd residing on two disks: One an ide > and one a scsi? Never tried it, but it should be possible. > > Cheers, > > Riley > > > Just installed 2.2.2-release on the only scsi drive in my > > system--disabled the ide controller in cmos from previous experience. > > > > Anyway, install goes ok, boots ok. Enabled the ide drive, which has > > 2.1.7 on it. Gets the boot prompt F1 -DOS, F2-2.1.7 and F5 2nd DISK. > > > > Press F5 and get "F?". I've seen this before, and done the fixes > > recommended by assuming this is a geometry problem. It doesn't seem > > to be. > > > > Used booteasy 2 beta (8?). No help. > > > > When F2 is pressed (ide drive 2.1.7) at the boot prompt I type in > > sd(0,a)/kernel and it boots wd(0,a)/kernel with no errors. That is > > it *seems* to take the arguement "sd(0,a)" but runs wd(0,a) and it > > ends up running 2.1.7, not 2.2.2-R. Try giving: 1:sd(0,a)/kernel at the boot prompt. Also make sure your SCSI disk is bootable (i.e. your BIOS should know about it). [snip] Never tried it myself, but it just may work, Nadav