Date: Fri, 15 Jun 2001 11:21:42 +0100 From: "Andy [Tecc Nops]" <andy@tecc.co.uk> To: <kstewart@urx.com> Cc: "FBSD-Q" <freebsd-questions@freebsd.org> Subject: RE: dual boot pain Message-ID: <NDBBKOKIGKLFGGPFHCGBIEKIDDAA.andy@tecc.co.uk> In-Reply-To: <3B29DEF7.B666ACC1@urx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> You use boot1 if it is on the same drive and boot0 > for different drives. I've have always spread my > system across all of the drives to have each drive > on a separate controller for speed. My / slice has > always been on the same drive and I use boot1 as > bootsect.bsd. There were some odd things that > happened in 3.x that I avoided. As in ur previous faqs on this I tried boot0 to boot the second drive but all it apeared to do was put a message saying "PRESS A KEY TO REBOOT". Like it's says on the tin, pressing a key did in fact reboot again! > I would have assumed that using boot0 as bootsect.bsd > would have booted off of your 2nd hd. There are several > people that come to mind that boot off of the 2nd hd. > I don't remember if they had to run boot0cfg or not. I tried various boot0cfg invokations, all failed. :( The only way I managed to boot the second drive was to set, in BIOS, the boot order as D,A,SCSI rather than C,A,SCSI. This worked but I didn't want the people using Windows have to do this to boot a machine. > Kent Regards Ak To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBKOKIGKLFGGPFHCGBIEKIDDAA.andy>