Subject: Re: take 2; which way should we go for /etc/rc...
To: None <tech-userlevel@netbsd.org>
From: Michael C. Richardson <mcr@sandelman.ottawa.on.ca>
List: tech-userlevel
Date: 12/03/1999 15:49:33
>>>>> "Luke" == Luke Mewburn <lukem@goanna.cs.rmit.edu.au> writes:
    Luke> c)	/etc/rc runs rcorder over /etc/init.d and runs scripts
    Luke> 	as necessary. (rc.sh and rc.shutdown.sh implements this)
    Luke> 	Pros:
    Luke> 		- thirdparty scripts (that support `start' and `stop'
    Luke> 		  work) with minor changes (need to add `PROVIDE:'
    Luke> 		  and `REQUIRE:' lines if ordering is necessary)
    Luke> 	Cons:
    Luke> 		- slower that b)
    Luke> 		- still needs minor changes to 3rdparty scripts
    Luke> 		  (you need to add the PROVIDE/REQUIRE lines)

  I don't like the runtime dependancy on rcorder.

    Luke> e)	/etc/rc is autogenerated from /etc/init.d/ containing a list of
    Luke> 	lines which just do "/etc/init.d/foo start; /etc/init.d/foo2 start",
    Luke> 	etc.
    Luke> 	Pros:

  This is my favorite.

   :!mcr!:            |  Cow#1: Are you worried about getting Mad Cow Disease?
   Michael Richardson |  Cow#2: No. I'm a duck.
 Home: mcr@sandelman.ottawa.on.ca. PGP key available.