> >> The learning curve [for /etc/init.d-style startup] is obscene.
> > But you don't *want* to edit the whole startup process.  You want to
> > edit the part you're looking at.
> 
> I _do_ want to edit the whole process at one point: when a new OS
> arrives.  They _always_ need sanitizing, often extensive.

no they don't...  the OSF/1 boxes that i run have _no_ init.d script
_modified_ from what DEC shipped (some are added by us, though).  my
NetBSD boxes have _no_ modifications to /etc/rc, from the base
distribution.

Why _make_ people modify the existing files to add something new
to their system configuration?  it makes them need to understand them,
it makes upgrading harder.

I'd say that the majority of the people who use rc-style scripts don't
modify the system-supplied contents much at all.  they may add to
them, they may tweak a few things, but at least 75% of the standard
system-provided code remains unchanged.  why _make_ them look at it,
if all they want to do is add the a package that needs a startup script?



> > A reasonably well built set of init.d files is rarely confusing; each
> > covers a specific subsystem, and if you want to edit "the network
> > stuff", it's probably all there.
> 
> Scattered across multiple files, though.
> 
> One file ifconfigs the interfaces.  Another starts up the router
> daemon.  A third fires up NFS.  A fourth starts inetd.  A fifth for
> AFS.  A sixth for that d*mn license manager that doesn't know how to
> run from inetd.  A seventh...I think you get the point. :-)

I dunno, i think i'd like them to all be seperate files.

lets me go into init.d, throw away AFS _really_ easily.  8-)


chris