Date: Fri, 2 Dec 2005 08:35:39 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Yar Tikhiy <yar@comp.chem.msu.su> Cc: freebsd-rc@freebsd.org Subject: Re: Adding /usr/local/etc/rc.d to the base rcorder Message-ID: <20051202163539.GA22464@odin.ac.hmc.edu> In-Reply-To: <20051202080604.GA12291@comp.chem.msu.su> References: <438C37E1.6010600@FreeBSD.org> <20051201003525.GB21393@odin.ac.hmc.edu> <438E4FCB.8060806@FreeBSD.org> <20051202080604.GA12291@comp.chem.msu.su>
next in thread | previous in thread | raw e-mail | index | archive | help
--3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 02, 2005 at 11:06:05AM +0300, Yar Tikhiy wrote: > On Wed, Nov 30, 2005 at 05:20:11PM -0800, Doug Barton wrote: > > > On Tue, Nov 29, 2005 at 03:13:37AM -0800, Doug Barton wrote: > > >=20 > > >>My patch to implement all this is at > > >>http://people.freebsd.org/~dougb/local-rcorder.diff. Comments are wel= come. > > >=20 > > >=20 > > > This looks pretty good to me. Thanks for working on this.=20 >=20 > Please accept my appreciation of your efforts, too! >=20 > > > A few comments: > > >=20 > > > - I have this vague feeling that we should replace most dependencies = on > > > mountcritremote with a new pseudo target like FILESYSTEMS or MOUNTS. > > > This isn't important. :) > >=20 > > Right, this can be revisited later if needed. The more I thought about = this > > the more I liked the concept of what JR suggested, although obviously I > > implemented it in a slightly different manner. I'm hesitant to add more > > pseudo-targets, as I think using mountcritremote is a good "clear bright > > line" for this purpose. I also have a fantasy down the road (not sure h= ow to > > implement it yet) of making the point to split early/late configurable.= For > > example, I can imagine a scenario where someone might want to put the s= plit > > at mountcritlocal. However, this is a good safe place to start. >=20 > With a pseudo-target for filesystems, will we still need the split > hardcoded in /etc/rc? Using a single run of rcorder should be > sufficient if all our rc.d scripts specify correct interdependencies > between each other. Using the pseudo-target would be a natural way > of doing so while keeping the possibility to move the split up and > down the boot sequence. You have to run rccorder twice because until mountcritremote (or an equivalent pseudo target) you aren't garenteed to have access to all the files rcorder needs to parse. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDkHfYXY6L6fI4GtQRApflAJ41qHUEghnbPbxFqybcBjSrCFv68wCgnrQk zraBHpofzYOSRTt6qI4QHys= =nEaA -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051202163539.GA22464>