From owner-freebsd-ports@FreeBSD.ORG Tue Feb 17 21:03:28 2004 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 5388916A4CE; Tue, 17 Feb 2004 21:03:28 -0800 (PST) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E0D643D1F; Tue, 17 Feb 2004 21:03:28 -0800 (PST) (envelope-from ade@FreeBSD.org) Received: from ts46-02-qdr1249.mdfrd.or.charter.com ([66.169.242.225] helo=[192.168.1.2]) by mail.lovett.com with asmtp (Exim 4.30; FreeBSD) id 1AtJrq-000BV7-PT; Wed, 18 Feb 2004 05:03:27 +0000 From: Ade Lovett To: "Simon L. Nielsen" In-Reply-To: <20040217222807.GA771@arthur.nitro.dk> References: <20040217193127.5655.qmail@laurel.tmseck.homedns.org> <87vfm5777l.fsf@gray.impulse.net> <20040217212137.GD719@laurel.tmseck.homedns.org> <20040217222807.GA771@arthur.nitro.dk> Content-Type: text/plain Message-Id: <1077080652.51446.4.camel@gorf.lovett.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 17 Feb 2004 21:04:12 -0800 Content-Transfer-Encoding: 7bit cc: freebsd-ports@freebsd.org Subject: Re: Feature Request: /usr/local/etc/rc.conf support X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 05:03:28 -0000 On Tue, 2004-02-17 at 14:28, Simon L. Nielsen wrote: > There is also the option of using the (yet) undocumented in FreeBSD [1] > /etc/rc.conf.d/service files. E.g. to enable rsyncd you would have > /etc/rc.conf.d/rsyncd with the variable rsyncd_enable="YES" (Note: I > haven't tested this, but I'm rather sure I'm reading the source and > NetBSD manual page corrrectly). Unfortunately, this is still (at least to the port) dinking outside of ${PREFIX} (either ${LOCALBASE} or ${X11BASE}), and is somewhat dirty. Since we already have (now) /etc/rc.d, /usr/local/etc/rc.d, and /usr/X11R6/etc/rc.d launching scripts left, right, and center, it does not seem unreasonable to have equivalent etc/rc.conf and etc/conf.d mechansisms, so that changes can be kept in isolation from each other. A considerable number of machines will, to one degree or another, consider anything outside of /usr/local and /usr/X11R6 (with few, well-documented exceptions) to be "off-limits" for ports, me included. I should be able to consider my "system drive" disposable, with just enough to get it up and talking to the rest of the system, which then brings the machine to real use by means of /usr/local (and, of course, /usr/X11R6) equivalents to the etcNG startup mechanism for the base system. -aDe