From owner-freebsd-www  Wed Mar 12 00:32:36 1997
Return-Path: <owner-freebsd-www>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA25702
          for www-outgoing; Wed, 12 Mar 1997 00:32:36 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA25693
          for <www@freebsd.org>; Wed, 12 Mar 1997 00:32:30 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id AAA16601; Wed, 12 Mar 1997 00:31:15 -0800 (PST)
To: RCB <rbeer@jaguar.cris.com>
cc: www@freebsd.org
Subject: Re: General comments 
In-reply-to: Your message of "Tue, 11 Mar 1997 23:09:06 PST."
             <199703120709.XAA26760@jaguar.cris.com> 
Date: Wed, 12 Mar 1997 00:31:14 -0800
Message-ID: <16598.858155474@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-www@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The  biggest "issue" I ran  into was installing  FreeBSD  at home on a
> 2-SCSI disk system.   My first scsi  drive is  for Windows, my  second
> scsi drive has FreeBSD  installed.  It was not clear  how to have  the
> FreeBSD boot manager installed on the first SCSI drive and allow it to
> boot either  the Win95 or  FreeBSD systems.  Reading  the handbook and

This has been cleaned up in the documentation - now it says that to do
this, you simply have to visit your first drive and make no changes to
the partition layout (unless you want some FreeBSD bits to actually
land on that drive) but select a boot manager.  That will do the trick
for you, in the same manner as RedHat and the others.

> That is about it.   Again,  great work.  After  all the  headaches and
> hours of wasted time due to  sloppy Linux distributions, poor testing,
> and extensively bloated kernels, I think I'll stick with FreeBSD.

Glad to hear it! :)

					Jordan