From owner-freebsd-current Tue Jul 29 21:30:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA06803 for current-outgoing; Tue, 29 Jul 1997 21:30:43 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06798 for ; Tue, 29 Jul 1997 21:30:34 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id OAA31416; Wed, 30 Jul 1997 14:26:49 +1000 Date: Wed, 30 Jul 1997 14:26:49 +1000 From: Bruce Evans Message-Id: <199707300426.OAA31416@godzilla.zeta.org.au> To: bde@zeta.org.au, terry@lambert.org Subject: Re: Multiple FreeBSD Systems on a Single Disk Cc: abial@korin.warman.org.pl, current@FreeBSD.ORG, rgrimes@GndRsh.aac.dev.com, sherwink@ix.netcom.com Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >And should be fixed (I've mentioned this before) to boot from the >> >first ACTIVE (flag 0x80) FreeBSD slice. Should be a trival amount >> >> That would mainly break certain configurations. The active flag >> should only be set for one partition, so you shouldn't have any active >> FreeBSD partitions if you have an active DOS partition. > >The boot managers (at least the one he's been pushing) set the >active partition to the one selected for boot. Mine doesn't :-). It stores the default partition number in its code and ignores the active flags. It passes a pointer to the partition being booted in es:si (same as booteasy), but the secondary bootstrap shouldn't assume this. Bruce