Date: Tue, 12 Jun 2001 17:16:13 +0200 From: "Karsten W. Rohrbach" <karsten@rohrbach.de> To: Warner Losh <imp@harmony.village.org> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: import NetBSD rc system Message-ID: <20010612171613.D63565@mail.webmonster.de> In-Reply-To: <200106120232.f5C2WLV43391@harmony.village.org>; from imp@harmony.village.org on Mon, Jun 11, 2001 at 08:32:21PM -0600 References: <20010611174717.A77956@laptop.6bone.nl> <1795096378.20010611154930@163.net> <3B2484EA.B1F04812@DougBarton.net> <20010611174717.A77956@laptop.6bone.nl> <200106111800.f5BI0il25446@billy-club.village.org> <200106111827.f5BIR2V38517@harmony.village.org> <3B25531D.501B0B05@bellatlantic.net> <200106112356.f5BNujV42614@harmony.village.org> <20010612032831.A11986@firedrake.org> <200106120232.f5C2WLV43391@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--vni90+aGYgRvsTuO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Warner Losh(imp@harmony.village.org)@2001.06.11 20:32:21 +0000: > Let me clarify. >=20 > 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. >=20 > Btw, for those that were asking, each file has lines like the > following: >=20 > # PROVIDE: ipmon > # REQUIRE: syslogd >=20 > which allows one to give a good dependency graph. =2E..if you are on a stock outofthebox distribution. if you do not use syslogd but a (better) replacement, these startup mimics start to suck=20 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 --=20 > 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.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 --vni90+aGYgRvsTuO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7JjI8M0BPTilkv0YRAjN/AJ9fmJFieg0mtbSaRXw7LGmWnq21LwCgoOso 3PcW/jxJcJUy8WPVBcw5QmA= =jUfF -----END PGP SIGNATURE----- --vni90+aGYgRvsTuO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010612171613.D63565>