From owner-freebsd-current Mon Jul 21 05:21:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA10488 for current-outgoing; Mon, 21 Jul 1997 05:21:42 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10479 for ; Mon, 21 Jul 1997 05:21:25 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id VAA10834; Mon, 21 Jul 1997 21:59:07 +1000 Date: Mon, 21 Jul 1997 21:59:07 +1000 From: Bruce Evans Message-Id: <199707211159.VAA10834@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, bde@zeta.org.au Subject: Re: switching to seral consoles Cc: ahd@kew.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * Yes, it would be a waste of time to update the man pages for work in > * progress. > >Well, if you say so. > > * See LINT for examples. > >And it's not a waste of time to upgrade LINT for work in progress? No, because new options should be put in LINT and maybe in options[.i386] so that they get used (at least at compile time), so LINT is the right place to look for all new options - if they aren't there, then the code controlled by them probably doesn't even compile :-). It's convenient to document new flags there, so that there is only one place to look for new things related to kernel configuration. >By the way, where can I find information on the "kernel.config" file >syntax? It's the same as userconfig command line syntax (where is that documented? :-), except the file must begin with the keyword USERCONFIG. The file normally ends qith `q' to quit userconfig. Option USERCONFIG_BOOT and the normal USEERCONFIG option must be configured for kernel.config to work. Misfeature: USERCONFIG_BOOT together with kernel.config starting and ending as above stops booting with -c from working. The config file is preferred and there is no way to switc to interactive mode. Bruce