In message <20000504225611.5968CDD@proven.weird.com>Greg A. Woods writes

>[ On Thursday, May 4, 2000 at 11:33:30 (-0700), Jonathan Stone wrote: ]
>
>I don't see the problem. You still only have to edit exactly the same
>number of files to make your cloned machine unique.   [...]

The common case for the changes I'm describing are *zero* files to
edit, and *one* file to move or copy.  rc.d on one handy machine has
70-odd scripts. It deosn't have an rc.conf.d, but the number of
distinct rc.conf.d files would be in that ballpark.

hint: 0 != 70 and 1 != 70.

Dd you have a point to make here, or not?



>If you're talking about re-cloning the machines to propogate a
>configuration change across all related machines then it should simply
>be a matter of creating a manifest of common files and using a simple
>one-line script to always copy all of the common files with every
>update.  Rdist would seem to be your best friend here, though of course
>any such tool will force you to be a little less ad hoc in your
>configuration management (which is supposed to be a *good* thing!).

I say that I *dont* *want* all the extra overhead and hassle you
mention.  In response, you criticize my sysadmin-ing as too "ad-hoc".
If you're trying to cause offense, you've succeeded.

Greg, why do you even participate on this list?
If you want SysV systems, you know where to find them.