Warner Losh([EMAIL PROTECTED])@2001.06.11 20:32:21 +0000:
> Let me clarify.
>
> If I were to add a few extra "modules" to the system. A, B, and C.
> If B needed A and C to start before it, then if I were to remove
> module A, B wouldn't start because its prereqs aren't there. These
> modules would be added, for example, in a package.
>
> Btw, for those that were asking, each file has lines like the
> following:
>
> # PROVIDE: ipmon
> # REQUIRE: syslogd
>
> which allows one to give a good dependency graph.
...if you are on a stock outofthebox distribution. if you do not use
syslogd but a (better) replacement, these startup mimics start to suck
bad ass as well.
i think the mostly statically wired rc system on freebsd is one of the
good points people actually use it. to add something yourself, it's not
a problem. don't get me wrong, but the point is:
a) it's a good thing[tm] for stabilizing the distribution's starup
behaviour
b) it will break most of the custom rc stuff other people do
of course, the migration path is to move it to /usr/local/etc/rc.d or to
/etc/rc.local, but what if i want to run my logger from rc? i write a
patch, apply it to the new dist and that's pretty it. if the rc stuff
gets too complicated it will become more difficult to find bugs, and for
lazy idiots like me it will be a PITA kinda thing to get all the "old"
script patches to work on a "new" rc system.
on the other hand it sounds reasonable when it will be easy to add
customized "modules" and to deactivate the standard ones. i am thinking
about something like
# PROVIDE: syslogd
# REQUIRE: daemontools
;-)
/k
--
> If it ain't broke, overclock it!
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.net/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- [EMAIL PROTECTED]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
PGP signature
