Date: Sun, 14 Sep 1997 15:51:51 +0930 From: Greg Lehey <grog@lemis.com> To: Mike Smith <mike@smith.net.au> Cc: Terry Lambert <tlambert@primenet.com>, brian@awfulhak.org, freebsd-hackers@FreeBSD.ORG Subject: Re: rc & rc.conf Message-ID: <19970914155151.53488@lemis.com> In-Reply-To: <199709140609.PAA00821@word.smith.net.au>; from Mike Smith on Sun, Sep 14, 1997 at 03:39:51PM %2B0930 References: <19970914151517.24823@lemis.com> <199709140609.PAA00821@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 14, 1997 at 03:39:51PM +0930, Mike Smith wrote: >> >> Yes, I'm not quite *that* stupid. We have two variables here: a >> -flags which is set with the flags, and an -enable which is set to >> either YES or NO. The original logic says "don't do it unless -enable >> is YES". Brian's saying "do it unless -enable is NO". I don't see an >> advantage in doing it this way, and I certainly don't see a disaster >> waiting to happen in the old way. > > The advantages are combined; consistency with all of the other similar > options, and by using "not NO", the _enable and _flags variables may > subsequently be combined. Well, sure, but he didn't do that. And that's the way it used to be with other flags, so somebody has deliberately specified an '-enable' and a '-flags' instead of combining them as a predicate. While checking this out, however, I came across the real reason: revision 1.129 date: 1997/06/18 16:01:18; author: pst; state: Exp; lines: +8 -3 Add cron_enable and inetd_enable flags to rc.conf. WARNING: don't update rc and forget to update rc.conf, or you won't be able to telnet back into your box after a reboot. Now I understand. But I don't think I agree. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970914155151.53488>