Date: Fri, 28 Aug 1998 22:28:22 -0700 (PDT) From: dima@best.net (Dima Ruban) To: mike@smith.net.au (Mike Smith) Cc: dima@best.net, mike@smith.net.au, dillon@backplane.com, jkh@time.cdrom.com, committers@FreeBSD.ORG Subject: Re: make.conf Message-ID: <199808290528.WAA20340@burka.rdy.com> In-Reply-To: <199808282216.WAA00640@word.smith.net.au> from Mike Smith at "Aug 28, 1998 10:16:48 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith writes: > In the following scenario, it requires an audit as Matt mentioned: > > - You perform an operating system upgrade, which updates /etc/rc.conf > - The upgrade adds a new service to the standard system startup > - The update of /etc/rc.conf enables this new service > - You do not want this new service enabled > > Because the existing rc.conf.local doesn't know about the new service, > it won't contain an override to turn it off. > > This case is likely to be so rare that while it's worth bearing in > mind, I can't see it as something to preclude using an automated update > tool. Well, I think all the new services should be disabled by default. An upgrade tool should mention about adding a new service but it should keep it disabled. If user will want to enable this service - he can do it manually. > > > -- > \\ 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 > > -- dima
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808290528.WAA20340>