Date: Fri, 25 Apr 1997 13:03:38 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: cjs@portal.ca (Curt Sampson) Cc: msmith@atrad.adelaide.edu.au, jkh@time.cdrom.com, hackers@freebsd.org Subject: Re: /etc/netstart bogons.. Message-ID: <199704250333.NAA00238@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.NEB.3.96.970424114719.5109I-100000@cynic.portal.ca> from Curt Sampson at "Apr 24, 97 11:54:15 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Curt Sampson stands accused of saying: > On Thu, 24 Apr 1997, Michael Smith wrote: > > > > Make a call now as to whether empty counts as set or unset. NetBSD's > > convention is that set-but-empty means to use the default value, > > whatever that is. > > Not really, no. Setting the variable to "DEFAULT" means use the > default value. Many of our variables are set to "NO" not to run > the program, "DEFAULT" to use reasonable defaults, or a list of > flags. Thus, having the variable set to "" or unset (they're the > same thing in /bin/sh) means `run the program with no command line > arguments.' My apologies; I was looking at a 1.2 machine when I wrote the initial. My only disagreement with that is that unset should mean either NO or DEFAULT, not yes and run with no arguments. It may possibly need to vary depending on context, ie. DTRT in the absence of configuration information. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704250333.NAA00238>