Date: Tue, 02 Feb 1999 17:13:42 +1030 (CST) From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Wes Peters <wes@softweyr.com> Cc: David Wolfskill <dhw@whistle.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: more modular rc/init/uninit system... Message-ID: <XFMail.990202171342.doconnor@gsoft.com.au> In-Reply-To: <36B695B3.E00558DC@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02-Feb-99 Wes Peters wrote: > > the scripts are a nice (useful IMHO :) place to start. > Well, then get started. Hacking up rc.* into rc.inet, rc.nfs, > etc. should be pretty straightforward work. It's just not all > that hard. ;^) Bah, I new someone would say that :) I just though that since someone seemed to be interested in doing it, then why don't they start with this, and then do the dependancy stuff later.. That way I get the benefits NOW =) > > (The idea being that the dependancy code just calls the scripts which are already in > > place) > That was what drove my idea to use a makefile; you could write the > start/stop scripts and express the dependencies in the makefile; the > start/stop scripts would be useful on their own. The disadvantage is > that you now have to edit the Makefile to add or remove something; > which we were trying to avoid. Yes, which could be problematic to do automatically :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990202171342.doconnor>