Date: Wed, 10 Feb 1999 08:29:34 -0600 From: Jon Hamilton <hamilton@pobox.com> To: Richard Wackerbarth <rkw@nomad.dataplex.net> Cc: John Fieber <jfieber@indiana.edu>, jack <jack@germanium.xtalwind.net>, current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. Message-ID: <19990210142934.6591A46B04@pobox.com> In-Reply-To: Your message of "Wed, 10 Feb 1999 07:28:42 CST." <Pine.BSF.4.05.9902100724470.1343-100000@nomad.dataplex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.05.9902100724470.1343-100000@nomad.dataplex.net>, Richar d Wackerbarth wrote: } } On Wed, 10 Feb 1999, John Fieber wrote: } } > On Wed, 10 Feb 1999, jack wrote: } > } > > If /etc/rc.conf only contains changes from the defaults when } > > man something_or_other tells the user to find and edit } > > something_or_other_flags in /etc/rc.conf the entry won't be } > > there to edit. } > } > Why must it contain only changes? Is there any reason it } > couldn't be a copy of the default rc.conf on a new installation? } } Alternately, it could be a copy of the default file with every item } commented out. That would provide the clues for those who need to } edit values and still not mess up the default behavior of a new install } with old options that might have changed but were not explicitly } overridden. But then you're right back where you started. Since rc.conf isn't supposed to be touched by the install/upgrade tools, it'll get out of date (and will become a hinderance rather than a help) as default settings change, and as settings are added/deleted. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990210142934.6591A46B04>