From owner-freebsd-bugs  Mon Jun  5 08:13:20 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA06242
          for bugs-outgoing; Mon, 5 Jun 1995 08:13:20 -0700
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA06229
          ; Mon, 5 Jun 1995 08:13:18 -0700
X-Authentication-Warning: freefall.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol
To: gordon@sneaky.lonestar.org (Gordon Burditt)
cc: bugs@FreeBSD.org
Subject: Re: Comments on 2.0.5-ALPHA boot floppy - Jun 4 
In-reply-to: Your message of "Mon, 05 Jun 95 07:34:00 CDT."
             <m0sIbMo-000E0iC@hammy.lonestar.org> 
Date: Mon, 05 Jun 1995 08:13:17 -0700
Message-ID: <6228.802365197@freefall.cdrom.com>
From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

> The boot disk:  FreeBSD 2.0.5-ALPHA, Jun 4.  This may be ambiguous,
> and thanks to ftpmail latency, I don't know the exact time but it 
> was sometime in the afternoon (Central Daylight Time).  
> cksum: 499586753 1228800 floppies/boot.flp

For future reference, see the README file in the UPDATES directory and
take the value for the first "Update:" line you see.  That's when the
floppies were "stamped".

> When I boot up, there are half a dozen lines of messages on the
> first screen just before it turns blue.  I can't read much more
> than "etc/sysinstall" in repeated tries.  The second screen
> shows that the system really DOES NOT LIKE my 1.1.5.1 disklabels
> and complains that several are "not entirely within the slice".
> Does this mean there is no chance for 1.1.5.1 and 2.0.5 to
> co-exist due to incompatible disklabel format, even if they

Not at all, it just means that 2.0.5 won't pass up the chance to
complain bitterly about them before grudgingly mounting them in
"compatability mode". :-)

> The system finds network devices 'cuaa0' and 'cuaa1' which 
> the -c option doesn't list.  Are these PPP/SLIP pseudo-devices?

Yes, they are.  That's why they're listed as "possible PPP/SLIP device" :-)

> When I exit, I get a complaint that it cannot open /etc/sysconfig.
> This happens even if I just read documentation and exit.
> Is this normal?

A small bug - I was always doing it, even when you didn't make any serious
changes.  I modified this to be more conservative for now.

> the tape to hold it all.  The main objectives right now are to 
> see if 2.0.5 is worth upgrading from 1.1.5.1, read the documentation, 
> figure out a good partition setup, and play around with specifying 
> a configuration without actually committing.

Very reasonable!  I encourange everyone to at least boot the
disk and read the docs!

> The (M)edia menu item refuses to let me select a tape drive
> as the device to load the distribution from unless there is
> a tape in the SCSI tape drive (see attachment at end for hardware
> details) just after the kernel finishes identifying all the devices.  
> Otherwise, I get a message 

This is kind of a fixed limitation.  I've taken your advice for now
and simply documented it in the hardware guide, thanks! :-)

> I like the -c option on boot, but maybe for 2.1 whether or not
> to save the changes permanently ought to be a settable option
> along with the changes.  This makes one-shot test configurations

Good idea.  Thanks for the feedback!

					Jordan