Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!nuchat!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.unix.admin
Subject: Re: Local rc scripts (was: Software installation opinions needed)
Message-ID: <W_26LS1@xds13.ferranti.com>
Date: 29 Sep 90 22:53:41 GMT
References: <312@pcad.UUCP> <ROWE.90Sep26052322@doc.cme.nist.gov> <KLM.90Sep26145601@goon.cme.nist.gov> <24601@uflorida.cis.ufl.EDU>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 24

The System V startup model might repay study.

	inittab ---> /etc/rc0
		     /etc/rc2 ---> /etc/rc2.d/S01MOUNTFSYS
				   /etc/rc2.d/S05RMTMPFILES
				   ...
		     /etc/rc3 ---> /etc/rc3.d/S08ina961
				   /etc/rc3.d/S20SV_onet
				   ...
		     ...

Run level 2 starts up all the multiuser stuff. Run level 3 is typically used
for the network level. An application program just needs to install a startup
file in /etc/rc?.d and it is automatically initialised. When shutting down,
then, it runs the rc files in reverse order and a different set of files is
run:

	inittab ---> /etc/rc2 ---> /etc/rc2.d/K20SV_onet
				   ...
		     /etc/rc0 ---> /etc/rc0.d/K98UMOUNTFSYS
				   ...

I'm really surprised that Sun and Berkeley haven't picked up on this yet. The
system for handling drivers is similarly clean...
-- 
Peter da Silva.   `-_-'
+1 713 274 5180.   'U`
peter@ferranti.com