Date: Thu, 27 May 2004 10:01:45 +0200 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Tobias Roth <roth@iam.unibe.ch> Cc: freebsd-rc@freebsd.org Subject: Re: ports and /etc/rc.d/ [was: Where to put my own startup script] Message-ID: <40B5A069.8080909@fillmore-labs.com> In-Reply-To: <20040527073700.GA16531@speedy.unibe.ch> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40B5A069.8080909>