From owner-freebsd-doc  Sun Nov 10 06:12:59 1996
Return-Path: owner-doc
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA10685
          for doc-outgoing; Sun, 10 Nov 1996 06:12:59 -0800 (PST)
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 GAA10672;
          Sun, 10 Nov 1996 06:12:53 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id GAA26305; Sun, 10 Nov 1996 06:12:54 -0800 (PST)
To: msmith@freebsd.org
cc: doc@freebsd.org
Subject: Anyone care to write a novice's guide to visual userconfig?
Date: Sun, 10 Nov 1996 06:12:53 -0800
Message-ID: <26303.847635173@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-doc@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Now that `boot -c' is essentially the default in the upcoming 2.1.6
and 2.2 boot floppies, it occurs to me that we're going to have to
document visual userconfig better if we're to have any hope of people
actually using it, rather than just whapping return at the first intro
screen.  Yes, the intro screen does say "if you're installing FreeBSD
for the first time, use visual userconfig to set the kernel to match
your hardware." but it doesn't say *how* to go about the process in a
more cookbook fashion.

Ideally, a page or two of text which led the user through a sample
session, taking care to impress upon the user just *why* it was
important to resolve all the conflicts and delete extraneous device
entries, would really help this process along and we could put it very
prominently in the README now that it's not an optional step.

Any takers?  Puhleeeze?  Thanks!!!

						Jordan