cvs commit: src/etc rc src/etc/defaults rc.conf src/etc/rc.d devfs dumpon initrandom rcconf.sh resolv src/share/man/man5 rc.conf.5 src/share/man/man8 diskless.8

[Doug Barton]

Alexander Leidinger wrote:
> Doug Barton <dougb at FreeBSD.org> wrote:
> 
>> Alexander Leidinger wrote:
>>> On Sat, 10 Dec 2005 15:02:27 -0800
>>> Doug Barton <dougb at freebsd.org> wrote:
>>>
>>>> Adam Gregoire wrote:
>>>>
>>>>> A diff for the addition of rcconf.sh to Obsoletefiles.inc.
>>>> Thanks. I want to hold off on that till we're 100% sure it can go 
>>>> away. I'm about 95% sure now.
>>>
>>> Just a little thing to think about: where do we want to handle this, in
>>> mergemaster, or in ObsoleteFiles.inc?
>>
>> Sorry it took so long to get back to you on this. Including the files 
>> in the obsolete file list won't hurt anything, and could make 
>> mergemaster easier for those that use the obsolete file service.
> 
> It could hurt people which use the obsolete file service, but don't use (or
> forget to use) mergemaster. There are other ways to shoot into the own foot
> (e.g. by not using mergemaster correctly), so should we care about this
> situation, or is this a "please follow the documented procedures" case?

Not having a script in /etc/rc.d that you need will create an error that is 
noticeable, and very unlikely to be fatal to the boot. Having a stale script 
(possibly with the same stale settings in rc.conf[.local] that used to be 
pertinent), could lead to very messy results.

I don't see anything wrong with adding rc.d stuff to the obsolete file list, 
but it's your call.

Doug


-- 

     This .signature sanitized for your protection