From owner-freebsd-questions Tue Nov 25 10:43:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA07013 for questions-outgoing; Tue, 25 Nov 1997 10:43:42 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA06982 for ; Tue, 25 Nov 1997 10:43:31 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id KAA17356; Tue, 25 Nov 1997 10:43:19 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Tue, 25 Nov 1997 10:43:19 -0800 (PST) From: Doug White Reply-To: Doug White To: Eli Lazich cc: Tim Pushor , questions@freebsd.org Subject: Re: Booting FreeBSD on second SCSI disk? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Nov 1997, Eli Lazich wrote: > Have you tried 'system commander' as I believe it is called. I seem to > remember somewhere in my readings that this would do what you want. The > NT boot loader certainly won't work (been there, done that) you might be > able to get the FBSD boot loader to accept a pointer to the NT active > partition, haven't quite investigated that one thoroughly myself. Unfortunately System Commander has bugs that break the FreeBSD bootblocks (it twiddles bit 4 in the system id), and FreeBSD expects that to be 0xA5 and nothing else. SysCommander changes it to 0xB5 for some twisted reason. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major