From owner-freebsd-hackers Mon Feb 1 21:33:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13303 for freebsd-hackers-outgoing; Mon, 1 Feb 1999 21:33:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from obie.softweyr.com ([204.68.178.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13283 for ; Mon, 1 Feb 1999 21:33:11 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id WAA04429; Mon, 1 Feb 1999 22:32:42 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36B68DFA.C14D590E@softweyr.com> Date: Mon, 01 Feb 1999 22:32:42 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Daniel O'Connor" CC: David Wolfskill , freebsd-hackers@FreeBSD.ORG Subject: Re: more modular rc/init/uninit system... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > > On 01-Feb-99 David Wolfskill wrote: > > So switch the logic: the "foo" script should be able to tell a > > sufficiently interested inquirer what services it depends on. > > > > If some of those have additional dependencies... well, I think we know > > how to do transitive closure on such dependency graphs. > > Hmmm.. how about getting the actual knobs committed and worry about the dependancy stuff > later? :) > > The problem with this stuff seems to be that everyone gets stuck on the 'ooh, the > dependancy stuff will suck' while not realising that 80% of the time it won't be needed.. The dependency stuff is the only reason for doing this; it's the shaft the knobs attach to. It's been pointed out many times before that doing it without the "dependency stuff" is of little value. > Perhaps we could also start making the files written into $PREFIX/etc/rc.d follow this > standard as a start, and then do the /etc/rc* stuff. Now that's a sparkling idea. I'm not sure we'll need the $PREFIX/etc/rc.d directories anymore, though, they were mostly a hack caused by our severe lack of an /etc/rc.d directory. I guess it won't add much to the complexity to retain them, but it won't really work to do it partially. I could, for instance, write a script for my Perforce server in a couple of minutes, but since it depends on "network", it's just not really going to work without the system stuff, too. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message