From owner-freebsd-current  Wed Oct  9 03:10:16 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA11533
          for current-outgoing; Wed, 9 Oct 1996 03:10:16 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA11527
          for <freebsd-current@freebsd.org>; Wed, 9 Oct 1996 03:10:14 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA21101; Wed, 9 Oct 1996 03:10:12 -0700 (PDT)
To: Charles Henrich <henrich@crh.cl.msu.edu>
cc: freebsd-current@freebsd.org
Subject: Re: 961006-SNAP comments 
In-reply-to: Your message of "Tue, 08 Oct 1996 13:10:27 EDT."
             <199610081710.NAA00777@crh.cl.msu.edu> 
Date: Wed, 09 Oct 1996 03:10:12 -0700
Message-ID: <21098.844855812@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The forced visual config on install is a horrible thing.  Forced config is a

I think this will be a matter of opinion, and you may rest assured that
I won't do anything to change it until I've collected a reasonable amount
of feedback on it.  If it's predominantly negative, then I'll certianly
nuke it.

Another thing that occurred to me about an hour after I released the
boot floppy was that detecting "Q" or "ESC" as special values for the
"any" key in intro and assume an immediate quit would probably be a
good idea.  Would that make you any happier?

For the rest of the users who just aren't RTFM'ing and setting their
hardware up properly (sending a message to us which then gets 5
replies all saying "Boot -c!"), I think this feature is just plain
mandatory.  It's not like I set your on-disk kernel up like this
either, it only happens once.  You must have a very low capacity for
tedium. :-)

> The installation process froze my keyboard (Flipping between alt-f1 alt-f2)
> about half way through the install, after it completed it popped my back to t
he
> main console and unlocked the keyboard.

Hmm, sounds like one for Soren.

> The install refused to update my /etc/ files because a piece of the
> installation failed.   That doesnt really make a whole lot of since, especial
ly
> as the piece that failed was compat21.  There was nothing I could figure out 

Yeah, I changed the policy on touching /etc to be a bit more paranoid,
and it looks like I'm checking more failure cases than I should be.
I'll fix it, thanks.

					Jordan