From owner-freebsd-questions Sat Jul 20 19:46:16 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA06178 for questions-outgoing; Sat, 20 Jul 1996 19:46:16 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA06162 for ; Sat, 20 Jul 1996 19:46:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id MAA21103; Sun, 21 Jul 1996 12:43:22 +1000 Date: Sun, 21 Jul 1996 12:43:22 +1000 From: Bruce Evans Message-Id: <199607210243.MAA21103@godzilla.zeta.org.au> To: Andries.Brouwer@cwi.nl, bde@zeta.org.au Subject: Re: installation fails Cc: questions@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I use OS/2 BM and LILO. Both boot only from drives that the BIOS >can access, that is in my case, from drives 0 and 1. > If this doesn't work, then any bootable disk, including the install > floppy, can be used to boot almost any disk: hit the space bar to make > the boot pause, then stare at the prompt to figure out or remind > yourself of the syntax, then type the destination, which should look > something like 5:sd(2,a)/kernel for the BIOS drive 5 of 0-5 and SCSI > drive 2 of 0-2. >This fails for the same reason. The BIOS does not know about >SCSI disks, so I have to boot a kernel from floppy or from >IDE disk 0 or 1 and tell that kernel where its root filesystem is. 0:sd(2,a)/kernel would work to boot from BIOS hard drive 0 to FreeBSD SCSI drive 2. Unfortunately, `0:' means hard drive 0 - there is no way to boot from floppy drive 0 to another drive even when you have loaded the boot program from floppy drive 0. Perhaps the BIOS drive number should be the full number - 0 for floppy drive 0 and 0x80 for hard drive 0. >For Linux one uses a command line parameter "root=/dev/sdc1" >to say that it must mount the first partition of the 3rd SCSI disk >as root filesystem. But what do I say to the FreeBSD kernel? In FreeBSD the boot parameters aren't preserved yet - you have to type them at every boot or modify the boot blocks. Bruce