> What do people think about an /etc/init.d/ file, either with or
> without run levels?  I think run levels are mostly useless, but others
> will certainly disagree.  I would consider writing an /etc/init.d
> startup method if there was interest.  I really think the
> /etc/rc.local method is just plain archaic, and each package SHOULD
> have its own startup/shutdown script.

I (sjg@zen) have done some of this already... or rather I've done a
frame work which I use on all boxes*.  I use the directory /etc/rc_d**
on all machines to hold the start/stop and support bits/pieces.
On all machines i have /etc/rc_local.d to contain boot time start/stop
stuff and /etc/shutdown.d and /etc/daily.d and ... you get the idea.

All the above are driven by /etc/rc.sh with links to the appropriate
name.

For booting BSD boxes, I have /etc/rc.d which contains the origianl
/etc/rc script and /etc/rc is a simple script that fixes the args to
rc.sh so that init need not be changed.

At one stage I played with breaking /etc/rc.d/rc and netstart etc into
appropriate bits - but decided it was a waste of time until there was
concensus about the desireability of doing so.  Given that the main
aim is to be able to add new bits etc.  

Some of the start/stop scripts I use on zen are ppp, rdate, ntp,
smapd, news, nfs_mounts, and www

Check out URL: 
	ftp://ftp.quick.com.au/pub/unix/

config-sh-1.08.tar.gz	contains my config tool (also driven by rc.sh)
			which sets up most of this and includes some
			of etc/rc_d
configs-example.tar.gz	contains an example config tree for the above
			and includes more of etc/rc_d.  This one is
			not kept up to date though.

* NetBSD,SunOS,Solaris,HP-UX...

** originally I used rc.d instead of rc_d, but Solaris and presumably
others, blindly execute everything in that directory so that had to
change :-)

--sjg