Subject: Re: post-installation and rc.d enhancements
To: None <tech-userlevel@netbsd.org>
From: Simon J. Gerraty <sjg@crufty.net>
List: tech-userlevel
Date: 04/17/2002 22:07:33
>> On Thu, 18 Apr 2002, Luke Mewburn wrote:

Sounds ok.

>The /etc/defaults/rc.pkg.conf would be modified by installation scripts,

I think this would be a big jump in the wrong direction.
The difficulty/undesirability of automagically frobbing a monolithic 
file without screwing local changes is a big part of why we now have
rc.d/*

There is nothing wrong with

/etc/rc.d/${class}_foo sourcing /etc/rc.conf.d/${class}_foo and/or
/etc/rc.${class}.conf which can source /etc/defaults/rc.${class}.conf
etc for class in "" pkg local etc (omit the _ if class == "" of course).
This provides a couple of points for a sysadmin to override defaults
while keeping the process of updating those defaults managable.
Note that for the sysadmin who just wants /etc/rc.conf to do it all,
they just make the other .conf files simply source that.

Thanks
--sjg