Now that sounz like a simple solution.:)) Paul...
> > Unless someone comes up with a scheme that tracks set membership and
> > allows us to add to that set, I think that we should stick to
> > the "simple"
> > approach.
> >
> > /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf"
> >
> > /etc/rc.conf is allowed to override this definition to
> > include additional
> > files such as "/etc/rc.conf.local"
> >
> > Those files get sucked in.
> >
> > - - -
> >
> > An alternate, and perhaps cleaner approach would be to always suck in
> > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those
> > files specified
> > in ${additional_rc_conf_files}.
>
> I still think we're chasing our tails with all this configuration stuff.
>
> Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if
> present). Don't have anything in /etc/defaults.rc.conf except default
> variable settings.
>
> The local admin can do what the hell they want in /etc/rc.conf, including
> putting in a bit of script to load /etc/rc.conf.local
> /etc/rc.conf.flavour_of_month etc.
>
> Paul.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
