Subject: Re: take 2; which way should we go for /etc/rc...
To: None <>
From: Hubert Feyrer <>
List: tech-userlevel
Date: 12/03/1999 00:49:08
On Thu, 2 Dec 1999, Luke Mewburn wrote:
> b)	/etc/rc is autogenerated from /etc/init.d at some stage
> 	(possibly by the developer who last changed an init.d
> 	script).

This *auto*generated scares me... you know, I do interrupt boot sometimes
with ^\, and I wouldn't want to see that happen right when that
autogeneration happens. 

> d)	/etc/rc runs /etc/rc3.d/S* in filename order.  (
> 	implements this). /etc/rc3.d is created from /etc/init.d by
> 	running `mkrc -s01` once.
> 	Pros:
> 		- ordering is obvious
> 		- allows people to install their own scripts in a
> 		  given order
> 	Cons:
> 		- considered to be an ugly warty sysvism by a lot of
> 		  people
> 		- if 3rdparty scripts are to be integrated into the
> 		  mkrc phase they need PROVIDE/REQUIRE lines.
> 		- not a true SYSV setup (no inittab/runlevels)

I'd prefer to have this on by default. And with this, at least I
personally and any pkg wouldn't have to 

 - edit rc.conf
 - run neither rcorder nor mkrc nor something else after dropping a script

> 	1. Which method do we ship with enabled by default?
> 		I'd argue for b) or c), possibly supporting d) or e),
> 		and strongly against f).

for me, d, see above.

> 	2. Do we support the other methods (e.g sample scripts in
> 	   /usr/share/samples/rc/) such as if we choose
> 		I'd say `yes', because there's no real harm in
> 		giving people the choice.

if it's clear that it needs some (minor) manual work to switch schemes,
sure, why not. /usr/share/examples/rc sound fine for that. I just want to
avoid a situation where a user asks "how do I start XXX on bootup", and he
gets answers for "edit rc.conf", "drop a script in .../*.d", etc.,
possibly confusing him without ends.

There's something else I wanted to ask: If I generate one start up scheme
somehow (/etc/rc, /etc/rc*.d/[SK]*, ...), and change /etc/rc.conf later,
will this be taken into account, or will i have to regenerate the scheme
file(s)? If the latter, this will seriously bite peopole used to "just"
edit /etc/rc.conf. 

 - Hubert

NetBSD - Better for your uptime than Viagra