>I REALLY don't like having them with the scripts, because part of the
>advantage of the scripts as I see it is that you can rdist them out to most
>machines, by just having an rdist target like /sbin/init.d or something,
>rather than having a complex setup where you don't rdist configuration
>files, but you do rdist these scripts, and....

Good point.  I forgot about that.

>I guess I'd like to see simplicity in all this -- my ideal setup would have
>one configuration file that setup what to run and not run, the startup scripts
>in /sbin/init.d, (I personally like the "script {start|stop}" method, but 

How about the following then.

/etc/config/pkg/*  <-- config files for package foo, if needed by that
		       package.

/etc/scripts/pkg   <-- package startup script

/etc/scripts.conf  <-- what to run and when to run it

I don't like the latter, but here are some thoughts on what it might
contain:

fsck:
ffs: fsck
network:
nfsclient: network
nfsserver: network ffs

This way you get a unique tag pkg: and a dependancies list.  A simple
C program could generate what is needed.  This file and the format
isn't what I think is best, just a possibility.  In fact, it kinda
sucks, doesn't it?  :)

--Michael

--
Michael Graff <explorer@flame.org>        NetBSD is the way to go!
PGP key on a key-server near you!         Rayshade the world!