From owner-freebsd-current  Tue Sep  2 22:38:28 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA19364
          for current-outgoing; Tue, 2 Sep 1997 22:38:28 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19356
          for <current@FreeBSD.ORG>; Tue, 2 Sep 1997 22:38:21 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id PAA31294; Wed, 3 Sep 1997 15:22:28 +1000
Date: Wed, 3 Sep 1997 15:22:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199709030522.PAA31294@godzilla.zeta.org.au>
To: jkh@time.cdrom.com, tom@uniserve.com
Subject: Re: /kernel.config documentation? WHere?
Cc: current@FreeBSD.ORG, mrcpu@cdsnet.net
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>   The kernel.config seems to be a derrivation of the dset stuff.  I think
>> it is just lines that are fed into the kernel user config cli.  Time to
>> read the source...
>
>That is correct.  It remains for Bruce to document this stuff he's
>added. :-)

This is only partly correct.  kernel.config has very little to do with
dset.  It should contain a magic header and lines that are fed into the
kernel user config cli.  It remains for jkh to document the magic header
and other gotchas.  I just made it easier to use the stuff that he added.
It is still hard to use.  E.g., when you enable USERCONFIG_BOOT then
entering the user config cli is forced, which is usually not what
you want.

Bruce