>> Add or delete...maybe.  Change, I especially disagree; the amount of
>> code you have to understand to change one component is more than the
>> amount in the whole thing under the old way.
> That's wrong -- all you need to understand is the programming
> interface and that can be documented in a few simple paragraphs (and
> indeed it is mostly documented now with internal comments in
> rc.subr).  The scripts themselves are black boxes that the average
> admin should never even read.

The same old "you don't need to know how it works under the hood, don't
bother your little head with that".

It just ain't so.

If the change I want to make is one that is provided for, I need to
know enough about how it works to be confident the documentation - if
any - is correct, that it's not going to spring a surprise on me and
automatically enable or disable something else I don't want because
someone else thought, incorrectly, "oh, but you can't possibly want
this without that".  Or that there aren't even any simple bugs lurking.

If the change I want to make is one that isn't provided for, matters
are even worse.  Or are you under the impression that you have
anticipated everything anyone can possibly want?

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B