From owner-freebsd-current  Tue Oct  8 10:44:01 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA09563
          for current-outgoing; Tue, 8 Oct 1996 10:44:01 -0700 (PDT)
Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA09545
          for <freebsd-current@freebsd.org>; Tue, 8 Oct 1996 10:43:56 -0700 (PDT)
Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id SAA01094; Tue, 8 Oct 1996 18:15:14 +0100
From: Luigi Rizzo <luigi@labinfo.iet.unipi.it>
Message-Id: <199610081715.SAA01094@labinfo.iet.unipi.it>
Subject: Re: 961006-SNAP comments
To: henrich@crh.cl.msu.edu (Charles Henrich)
Date: Tue, 8 Oct 1996 18:15:14 +0100 (MET)
Cc: freebsd-current@freebsd.org
In-Reply-To: <199610081710.NAA00777@crh.cl.msu.edu> from "Charles Henrich" at Oct 8, 96 01:10:08 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
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
> bad idea, especially when its not neccesary for most and confuses lots of
> people.  Secondly forcing me into the visual mode instead of command line was
> just tedium.

Let me disagree on this. I am fond of command line interfaces too,
but you have to consider that most people (probably less expert
than you) think differently.  I also believe forced config is usual.

The only thing I miss is probably a one-keystroke quit (Skip ?)
option which does not require you to confirm things if nothing has
changed (Hint hint...).

> The install refused to update my /etc/ files because a piece of the
> installation failed.   That doesnt really make a whole lot of since, especially
> as the piece that failed was compat21.  There was nothing I could figure out to
> do to get it to go back and write out the /etc files.

Agreed. This is a problem in that it leaves the install process
halfway through. It is probably more sensible to update etc files
in any case.

I also experienced difficulties in writing the boot manager (booteasy)
on my 2GB drive. I followed the standard procedure as usual (did
it twice) with no effect. Apparently, though, I can write a working
bootmanager with the "Write" option in the "Partition" menu.

Finally, a note on the computation of "default" partitions. It looks like
computations are based on memory size rather than on disk space. I have
tried to install on a 2GB disk and with 8MB ram, resulting in 28MB of
swap. I'd probably make it compute a larger swap area if the FreeBSD
slice is big enough. Say, 5..10% of the slice ?

	Luigi
====================================================================
Luigi Rizzo                     Dip. di Ingegneria dell'Informazione
email: luigi@iet.unipi.it       Universita' di Pisa
tel: +39-50-568533              via Diotisalvi 2, 56126 PISA (Italy)
fax: +39-50-568522              http://www.iet.unipi.it/~luigi/
====================================================================