From owner-freebsd-hackers  Fri Apr 25 21:31:39 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA04603
          for hackers-outgoing; Fri, 25 Apr 1997 21:31:39 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA04586
          for <hackers@freebsd.org>; Fri, 25 Apr 1997 21:31:36 -0700 (PDT)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA13484; Fri, 25 Apr 1997 21:31:24 -0700 (PDT)
To: "Jeffrey J. Mountin" <sysop@mixcom.com>
cc: Curt Sampson <cjs@portal.ca>, hackers@freebsd.org
Subject: Re: /etc/netstart bogons.. 
In-reply-to: Your message of "Fri, 25 Apr 1997 22:53:03 CDT."
             <3.0.32.19970425225302.00b22474@mixcom.com> 
Date: Fri, 25 Apr 1997 21:31:24 -0700
Message-ID: <13482.862029084@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> At 12:09 PM 4/24/97 -0700, Jordan K. Hubbard wrote:
> >OK, I haven't done anything with DEFAULT so far but here's the
> >rest of my changes relative to FreeBSD.
> 
> How about " " for no flags and then have default=NO for "" checking?

I'm not sure why NO is necessary if it causes no special expansion of
the flags.  Again, I'm trying to avoid any and all "dual use" of
variables, only having "NO" be a special value in non-boolean
situations when there's really no other reasonable way of doing it,
e.g.  I either have a filename parameter for something or I have "NO"
to denote that the option is turned off entirely.  Those are kinda
evil, from a conceptual standpoint, but there are 3-4 instances where
a foo_enable and a foo was just too redundant, and there are no
DEFAULT cases for them in any event so the point is kinda moot.

					Jordan