Date: Fri, 28 Aug 1998 21:40:59 +0000 From: Mike Smith <mike@smith.net.au> To: Matthew Dillon <dillon@backplane.com> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, Mike Smith <mike@smith.net.au>, committers@FreeBSD.org Subject: Re: make.conf Message-ID: <199808282141.VAA00419@word.smith.net.au> In-Reply-To: Your message of "Fri, 28 Aug 1998 19:51:30 MST." <199808290251.TAA21595@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> : * In general, No auditing of rc.conf.local is necessary. No merging, > : no editing, no nothing. In rare cases someone may turn on something > : in rc.conf that we may want to turn off in rc.conf.local, but we > : haven't come across such a case yet even when drastic changes are > : being made to rc.conf by the committers. > > I should make a correction here... after the initial turning off of > certain basic services turned on in rc.conf.local, that is. Once you've > set up your base overrides in rc.conf.local, you generally don't have > to mess with it during future upgrades even if the distribution rc.conf > file goes through major changes. That would imply a minimum of conflict between an automatically upgraded /etc/rc.conf and your scheme; because you leave /etc/rc.conf untouched, the upgrade would simply migrate it to the newer version, but your overrides would be left untouched. The one difficult case would be where a new addition to /etc/rc.conf was made which enabled a service which you wanted disabled. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808282141.VAA00419>