init.d, rc0.d, ... rc6.d

[Sen Nagata <sen_ml@eccosys.com>]

hello-

  i've been wondering what the advantages and disadvantages are w.r.t.
organizing the run-level changing/initialization scripts in the current
manner.

  right now there are a number of scripts stored in init.d which are
referenced by symbolic links from each of the rc*.d directories, right?

  what kind of advantages does this kind of approach have compared to
having a single file for each run level (or even one file for all
runlevels) describing which scripts to run (as well as the order to run
them in)?

  besides having to 'lock' and parse a file describing what is needed
for a single run level (which it seems could be dealt w/ by providing
adequate routines that everyone uses), what are other demerits to taking
the 'single-file' approach?  (leaving out the fact that if one were to
switch to such a scheme existing code might need to be modified)

-sen


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .