From owner-freebsd-current  Mon Jul 24 20:26:48 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id UAA05123
          for current-outgoing; Mon, 24 Jul 1995 20:26:48 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id UAA05117
          for <current@FreeBSD.org>; Mon, 24 Jul 1995 20:26:46 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id UAA03131; Mon, 24 Jul 1995 20:25:19 -0700
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: current@FreeBSD.org
Subject: Re: Knobs in /etc/sysconfig 
In-reply-to: Your message of "Tue, 25 Jul 1995 12:46:46 +0930."
             <199507250316.MAA01538@genesis.atrad.adelaide.edu.au> 
Date: Mon, 24 Jul 1995 20:25:18 -0700
Message-ID: <3128.806642718@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: current-owner@FreeBSD.org
Precedence: bulk

> (Unless I'm mistraken, the 'x' is a historic wart, and test can now handle
> empty arguments...)

Sorry, historical habit with the sh code I write.. :-)

> Please ensure that the default "yes" values are documented in the comments
> preceeding each knob; preferably in some standard format, eg:
> 
> # default: <value>

Sounds reasonable..  We still need to go through and ethnically clense
our handling of variables in general, actually.  It would be nice if
there was a STANDARD NAMING CONVENTION that told one whether or not a
given variable was a Boolean, a list of arguments, a list of things
that had their own sub-variables (like the network_interfaces var),
etc.

Probably the time to do that is now before it gets too big, but I'm
also not going to hold my breath.  It's work.

					Jordan