From owner-freebsd-rc@FreeBSD.ORG Thu May 27 01:01:54 2004 Return-Path: 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 3C70416A4CE; Thu, 27 May 2004 01:01:54 -0700 (PDT) Received: from fillmore.dyndns.org (port-212-202-49-130.reverse.qsc.de [212.202.49.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id F185043D4C; Thu, 27 May 2004 01:01:53 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.34; FreeBSD) id 1BTFpi-000CWe-IB; Thu, 27 May 2004 10:01:49 +0200 Message-ID: <40B5A069.8080909@fillmore-labs.com> Date: Thu, 27 May 2004 10:01:45 +0200 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Tobias Roth References: <40B2B7D4.5040106@users.sourceforge.net> <20040525210812.9728A5D08@ptavv.es.net> <20040526181624.GB55179@empiric.dek.spc.org> <40B5899E.7030506@fillmore-labs.com> <20040527073700.GA16531@speedy.unibe.ch> In-Reply-To: <20040527073700.GA16531@speedy.unibe.ch> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: freebsd-current@freebsd.org cc: freebsd-rc@freebsd.org Subject: Re: ports and /etc/rc.d/ [was: Where to put my own startup script] X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 27 May 2004 08:01:54 -0000 Tobias Roth wrote: > [...] > > 1) ports startup scripts use rc.subr and get a common structure (good) > 2) with a common structure, rcorder can be used for ports as well (good) > 3) /etc/rc.d/ and /usr/etc/rc.d/ get mixed up (bad) You meant /usr/local/etc/rc.d/ here? > 4) ports can be started early in the boot process (good, ie for things like > racoon) > 5) /etc/rc.conf contains directions about ports and is not just a subset of > /etc/defaults/rc.conf anymore (bad, same thing as 3) > > we tend towards 1) already. once a decision about the other points has been > taken, what's left is that all ports are (slowly) converted to this. > an update to the porters handbook and after a while, a warning when an > old-style startup script will be executed is the way to go. > > 2) will be very nice. PR 56736 from eik seems to address this very > elegantly. ports that need to be started early can be started directly after > the dummy PORTS dependency, all others that do not explicitly request a > specific startup order should be started at the end of rc.d/. this of > course also solves 4). You should not really use PORTS, but whatever you need to run. > [...] > > now, shouldn't racoon be started before mountcritremote? #$%#!#, i think > i just shot myself in the foot. comments please :-) i am sure that can > be fixed elegantly as well. The problem here is that /usr might not be a local filesystem, so touching anything there before mountcritremote is not a really good idea. -Oliver