Subject: RE: Summary: Third-party rc.d scripts
To: Tim Rightnour <firstname.lastname@example.org>
From: Frederick Bruckman <email@example.com>
Date: 02/08/2002 08:46:09
On Fri, 8 Feb 2002, Tim Rightnour wrote:
> Sushi wants to understand the format of rc.conf in order to generate a pretty
> display that lets the user modify it. Currently, this is accomplished by
> manually keeping rc.conf and the form file for sushi in sync. (if you have
> suggestions on other ways to do this, I suggest you look at the problem in
> detail before launching them at me)
> Therefore, if you just start tossing new defaults onto the end of
> /etc/defaults/rc.conf.default, sushi will have no clue what they are, and not
> be able to set them.
I think there won't ever be that many package rc.d scripts. We could
just list all of them in basesrc/etc/defaults/rc.conf, and in the
corresponding file for sushi. This way, 1) the defaults/rc.conf (and the
form file for sushi?) only gets frobbed if it's out of date, 2) updating
the base system won't lose the defaults. Same principle if it's chosen
instead to use defaults/rc.pkg.conf, included by defaults/rc.conf.
> But it's important we don't forget about this. If we go and add features to
> the system, but don't let the users set them via the tools supplied, we are
> doing them a disservice, and it's not a complete solution.