Subject: Re: more work in rc.d [was Re: rc, rc.shutdown proposed change]
To: None <tech-userlevel@netbsd.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
List: tech-userlevel
Date: 03/13/2000 12:11:35
> [.../etc/rc.d.../etc/rc.local.d.../etc/rc.pkg.d.../etc/init.d...]
> Oh and yes rc*.conf should die.
I don't recall any conclusion to the debate on SysV-style startup
scripts...but this discussion sounds ominous. Does it mean that NetBSD
is shortly going to screw over sites for whom a monolithic startup
script is the right way? (Approximately, sites for which human
manipulation of the startup sequence is more important than mechanical
manipulation thereof.)
I saw one remark about "rcorder /etc/rc.d/*", which sounds even worse:
broken-out startup scripts run from a single startup script combine the
worst features of both. You lose the human and speed benefits of
all-in-one-place but at the same time you don't gain the mechanical
benefits of being able to count on "editing" the startup "script" by
frobbing files in a directory, because you have no way of telling what
may have been done to the driving script.
der Mouse
mouse@rodents.montreal.qc.ca
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B