From owner-freebsd-questions  Sat Jan  6 09:06:15 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA04279
          for questions-outgoing; Sat, 6 Jan 1996 09:06:15 -0800 (PST)
Received: from zork.tiac.net (zork.tiac.net [199.0.65.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA04273
          for <questions@freebsd.org>; Sat, 6 Jan 1996 09:06:08 -0800 (PST)
Received: from momcat.swaa.com (tarbet.tiac.net [199.3.140.106]) by zork.tiac.net (8.6.9/8.6.6.Beta9) with SMTP id MAA08519; Sat, 6 Jan 1996 12:06:11 -0500
Message-ID: <MAPI.Id.0016.006f6d63617420204142313330303030@MAPI.to.RFC822>
Priority: Normal
To: questions@freebsd.org
MIME-Version: 1.0
From: Margaret Tarbet <tarbet@swaa.com>
Subject: update on 2.1 install problem
Date: Sat, 06 Jan 96 12:09:37 EST
Content-Type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT"
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
Precedence: bulk

Hello all...

Recently i wrote of the difficulty i had in installing 2.1
on my dev machine.  I thought y'all might like an update.

I still haven't actually looked to see what was broken
about my first attempt to install, but i fixed it in a
practical way:  i specifed the fbsd boot manager instead of
the vanilla boot block.  I forgot to de-install System
Commander and restore the dos boot block before doing the
fbsd install and when i realised my oversight, midway
through, i thought that i'd have some fixing up to do
later, as well as a kludgey boot process if indeed it worked
at all.  But, interestingly enough, that didn't prove to be
the case:  it did work, and not only did syscmdr adopt the
fbsd block without any extra intervention on my part, there's
no two-stage selection involved...fbsd boot manager doesn't
appear to be there at all!  So evidently my mental model of 
how syscmdr works needs to be adjusted at least, and i
need to report that install bug.

So, anyhow, if anyone else is planning to use a third-party
boot manager, try specifying the fbsd boot manager anyway
when you install fbsd.  Counter-intuitive, but it worked
for me.

Thanks to those who responded with suggestions, it was a
quite a surprise(!) to find out that questions@freebsd is an
alias for everyone@everywhere :-)

                                regards,
                                =margaret