Subject: Re: take 2; which way should we go for /etc/rc...
To: None <email@example.com>
From: Luke Mewburn <firstname.lastname@example.org>
Date: 12/03/1999 11:51:56
Hubert Feyrer writes:
> 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.
Autogeneration doesn't happen at BOOT TIME. It's a MANUAL PROCESS done
at some stage during the system build (e.g, by a developer, or by the
system admin when they install the system, or ...). Doing autogeneration
each boot would be ... dangerous!
I thought that was obvious in the paragraph above, but I was
obviously mistaken :-)
> 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.
Yes. checkyesno is used in all the system scripts. If you just change
stuff in /etc/rc.conf it will work. In the `generate rc' or `generate
rc3.d/' approach, you only have to regenerate if you add or remove
stuff from /etc/init.d, or change the rcorder(8) dependancy lines (like