From owner-freebsd-rc@FreeBSD.ORG Fri Dec 2 08:06:19 2005 Return-Path: X-Original-To: freebsd-rc@freebsd.org Delivered-To: freebsd-rc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC97316A41F; Fri, 2 Dec 2005 08:06:19 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A8B743D83; Fri, 2 Dec 2005 08:06:13 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jB2868kT012804; Fri, 2 Dec 2005 11:06:08 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jB2865tK012803; Fri, 2 Dec 2005 11:06:05 +0300 (MSK) (envelope-from yar) Date: Fri, 2 Dec 2005 11:06:05 +0300 From: Yar Tikhiy To: Doug Barton Message-ID: <20051202080604.GA12291@comp.chem.msu.su> References: <438C37E1.6010600@FreeBSD.org> <20051201003525.GB21393@odin.ac.hmc.edu> <438E4FCB.8060806@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438E4FCB.8060806@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: freebsd-rc@freebsd.org Subject: Re: Adding /usr/local/etc/rc.d to the base rcorder X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 08:06:19 -0000 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: > > > >>My patch to implement all this is at > >>http://people.freebsd.org/~dougb/local-rcorder.diff. Comments are welcome. > > > > > > This looks pretty good to me. Thanks for working on this. Please accept my appreciation of your efforts, too! > > A few comments: > > > > - 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. :) > > 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 how 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 split > at mountcritlocal. However, this is a good safe place to start. 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. -- Yar