Date: Mon, 25 Sep 1995 23:05:04 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: peter@taronga.com (Peter da Silva) Cc: hackers@freebsd.org Subject: Re: ports startup scripts Message-ID: <199509260605.XAA09028@ref.tfs.com> In-Reply-To: <199509260347.WAA27526@bonkers.taronga.com> from "Peter da Silva" at Sep 25, 95 10:47:08 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 1) Explicit (complex) numbering in the single directory > > Experience shows that the parenthetical (complex) is just not true. > > > 2) Mirrors of the "init.d" directory into other directories "rcN.d" > > with explicit numbering in those > > This is nice. > > > 3) Script to run from that directory to control order. > > That's where we are now. > > > 4) Control file. > > That's identical to #3. > > > #2 - You get whole directories of symlinks. Yuk. Lots of headaches. > > A name in a file is a symbolic link, too. Except it's harder to add. > > > #4 Works very simply. Ports can add one line to a config file, > > And where pray tell do they add the line? At the end? Then you might as > well go back to #1 except now they'll be in random order. And anywhere > else just doesn't bear thinking about. > > > Why complicate things? > > Dependencies on startup order. > use Make to start the system each module supplies a file that is included into the master makefile (which is generated..) echo "# Hi there.. This is Eddy your Shipboard Computer " >/tmp/boot.mk for i in /init.mk/* do echo ".include $i" >>/tmp/boot.mk done make -k -f /tmp/boot.mk :) -------------------------------- cat net.mk net: <whatever ifconfig is dependent on> ifconfig .... nsfclient: net nfsiod -n 4 heh heh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509260605.XAA09028>