On Sun, Mar 18, 2007 at 11:57:10AM -0400, Greg Troxel wrote:
> 
> > Adding /etc/rc.d.local/ offers only one supplementary indication,
> > without adding overhead or changing behavior. It is all benefits.
> 
> This seems like a reasonable step, even though it fails to address
> site and pkgsrc.  Perhaps /etc/rc.d.pkgsrc should also exist, with
> pkgsrc putting rc.d scripts there.

You've got a point here since, for example, I do not like the rc.d/pgsql
script provided by pkgsrc and add my own. So merging all in
/etc/rc.d.local will lead to the same hiatus: is this a "local" script
or a pkgsrc one, and can I allow pkgsrc to overwrite or not?

It would be cleaner to have also a /etc/rc.d.pksrc. But won't people
find that this is "too much"?

Other problem. The "lazzy" slope will be to add a
/etc/rc.defaults.pkgsrc with all the definitions for half the Google
cache possible daemons and, for "easyness", to add by default all the
script to /etc/rc.d.pkgsrc/. This will lead to a start up time I simply
don't want to imagine since rcorder(8) will order everything, and rc(8)
will call every script.

IFF a /etc/rc.defaults.pkgsrc is used to add and remove chunks of definitions
for the variables setting of an installed/removed package in
/etc/rc.d.pkgsrc/, decision being taken in /etc/rc.conf, and default
being always NO for pkgsrc installed daemons, that could do.
-- 
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
                 http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C