On Mon, 31 Jul 2000, Greg A. Woods wrote:

> [ rc.conf defaults ]
>
> The other "solution" is to do something like what Postfix does that'll
> keep the same full /etc/rc.conf template and encourage people to edit it
> directly.  Then provide a command (ala 'postconf -n') that'll print only
> the non-default settings so that these can be applied to a new copy of
> /etc/rc.conf.  This probably does mean storing the defaults directly in
> the script(s) in such a way that they can still be examined after the
> current configuration is loaded, and indeed so that a template
> /etc/rc.conf can be generated directly with all the defaults.  Then so
> long as the old scripts are kept during an upgrade the admin can use
> them to dump the old configuration changes and make sure that they've
> all been preserved once they've been applied to the new /etc/rc.conf and
> indeed much of this could be automated in the long run.

	At the very least it would be a big help to ship a second copy
	of rc.conf - maybe /etc/rc.conf.default or somewhere in
	/usr/share/examples... so that if people want to write tools
	they can depend on an original version being around.

                David/absolute
			       -- www.netbsd.org: A pmap for every occasion --