Date: Wed, 2 Dec 1998 10:26:43 -0500 (EST) From: ADRIAN Filipi-Martin <adrian@ubergeeks.com> To: Terry Lambert <tlambert@primenet.com> Cc: eivind@yes.no, rssh@grad.kiev.ua, grog@lemis.com, dyson@iquest.net, wes@softweyr.com, hackers@FreeBSD.ORG Subject: Re: System V init (was: Linux to be deployed in Mexican schools; Where was FreeBSD?) Message-ID: <Pine.BSF.3.96.981202101826.9233C-100000@lorax.ubergeeks.com> In-Reply-To: <199812011857.LAA26942@usr07.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 1 Dec 1998, Terry Lambert wrote:
> > Second, the dynamic ordering of dependencies is nice, but having
> > the ordering information spread accross every file in rc.d makes it very
> > hard to speak with authority on just what is going to happen and in what
> > order. Pulling this ordering information up into a central place would be
> > much prefered. I also content that it would be more maintainable over the
> > long haul.
>
> I believe this could be addressed with a "-n" option, where it tells
> you what it would do, but doesn't actually do it. In other words,
> it's an implementation detail, and fairly irrelevent.
Great minds think alike. It's already in the version I'm working on.
> > scripts=""
> > scripts="${scripts} ccdconfig"
> > scripts="${scripts} swapon"
> > scripts="${scripts} autoboot"
> > scripts="${scripts} mount_root"
> > scripts="${scripts} mount_local"
> > scripts="${scripts} start_net"
> > scripts="${scripts} mount_nfs"
> > ...
> > scripts="${scripts} rc.local"
> >
> > for i in ${scripts}; do
> > /etc/rc.d/$i start
> > done
> >
> > The order of execution is easily grasped. For rc.shutdown, all
> > you need to do is reverse the list and loop with "stop" as the argument.
>
> This fails to represent the fact that you shouldn't start something
> which consumes "syslog" services before you start "syslogd", or a
> fax-to-mail gateway that consumes "SMTP" services before the SMTP
> server.
I wasn't going to do dependencies, but I might think about it.
They way I'm working things, it should be easy to at add the end.
> Finally, it fails to be extensible in the face of a read-only root
> partition, and, in some situations, NFS based mounts following a
My implementation will be less naive.
Thanks for the input.
Adrian
--
[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]
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?Pine.BSF.3.96.981202101826.9233C-100000>