From owner-freebsd-current  Sat Apr  1 04:32:34 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09356 for current-outgoing; Sat, 1 Apr 1995 04:32:34 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA09347 for <freebsd-current@FreeBSD.org>; Sat, 1 Apr 1995 04:32:22 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA08606; Sat, 1 Apr 1995 22:30:09 +1000
Date: Sat, 1 Apr 1995 22:30:09 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504011230.WAA08606@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.org, taob@gate.sinica.edu.tw
Subject: Re: New installation notes
Sender: current-owner@FreeBSD.org
Precedence: bulk

>    When the installer finally did come up, both drives showed up as
>sd0 and sd1 with the expected partitioning.  I fdisked sd0 and told it
>to use the entire drive for FreeBSD.  However, when I went to
>disklabel sd0, it defaulted with an MSDOS partition (sd0e) the size of
>the entire slice.  I deleted it and then went to allocate the
>filesystems.  Was I supposed to leave a small MS-DOS filesystem for
>the boot manager?  My intention was to have the boot manager come up
>and ask me to select DOS (booting off the second drive) or BSD
>(booting off the first drive).  Is this possible, and if so, how do I
>specify this?  Does it have something to do with importing an MS-DOS
>disk slice as a FreeBSD partition?  Currently, the computer boots
>straight into FreeBSD.

The whole drive can't be used for BSD if there is a boot manager
because if the whole drive is used for BSD then there is no space
left for the boot manager.  An MSDOS partition shouldn't be necessary
and shouldn't be created.  Just create a BSD partition starting
somewhere after the boot manager.

Bruce