From owner-freebsd-ports@FreeBSD.ORG Sun Nov 30 21:25:35 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E947816A4CE; Sun, 30 Nov 2003 21:25:35 -0800 (PST) Received: from saturn.criticalmagic.com (saturn.criticalmagic.com [68.213.16.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84DFB43FBF; Sun, 30 Nov 2003 21:25:34 -0800 (PST) (envelope-from richardcoleman@mindspring.com) Received: from mindspring.com (titan.criticalmagic.com [68.213.16.23]) by saturn.criticalmagic.com (Postfix) with ESMTP id BFA643BD10; Mon, 1 Dec 2003 00:25:33 -0500 (EST) Message-ID: <3FCAD0DC.9090104@mindspring.com> Date: Mon, 01 Dec 2003 00:25:48 -0500 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: Oliver Eikemeier cc: Kris Kennaway cc: freebsd-current@freebsd.org cc: "Maxim M. Kazachek" Subject: Re: Ports startup scripts in /etc/rc.d (Re: 5.2-BETA and related ports issues) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richardcoleman@mindspring.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Dec 2003 05:25:36 -0000 Robert Watson wrote: > For 5.2-CURRENT, I think we should revisit this issue with one of the > following conclusions winning out, and the rest being discarded as > flame-bait: > > (1) Combine / and /usr into a single file system by default, and add > /usr/local/etc/rc.d to the search order, with appropriate hacks to > handle old-style scripts. The devil will be in the bikeshed, but the > implementation is easy, except for the bit where we explain that > NFS-mounted /usr/local won't work too well. > > (2) Reevaluate the order at routine points in the boot where new scripts > might now be available (due to file system mounts or whatever). > Essentially "insert the new cards into the deck, and shuffle". This > requires rethinking of our current approach, which assumes a static > order is created once at the start of the boot by rcorder(8). The > devil will be in the big picture *and* the details of the > implementation. > > (3) Add /local/etc/rc.d or /local/rc.d or /etc/local/rc.d or the like, a > new directory that third party applications are allowed to modify > during install, and that will be present for the creation of the > static ordering by rcorder(8) early in the boot. The devil will be in > the bikeshed, but the implementation is easy. > > (4) Continue to ignore the issue and let some ports install into /etc/rc.d > and consider them unorthodox, incorrect, but something we can > overlook. The devil isn't here, or at least, if it is, we'll overlook > it. > > I'm actually leaning towards (2) as being the best solution, as it's easy > and functional. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Senior Research Scientist, McAfee Research I think this message sums up the options quite nicely. I like option 2 the best, with option 3 a close second. I think either would be an acceptable compromise. Option 1 abandons the ability for read-only /usr, which many people like. That and the NFS problems that Robert mentioned should rule this out. But I like anything over doing nothing (option 4). Richard Coleman richardcoleman@mindspring.com