Date: Mon, 22 Mar 1999 04:23:15 -0600 (CST) From: Richard Wackerbarth <rkw@dataplex.net> To: John Baldwin <jobaldwi@vt.edu> Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Subject: Re: /etc/rc.conf, take 46! Message-ID: <Pine.BSF.4.05.9903220415270.72040-100000@nomad.dataplex.net> In-Reply-To: <XFMail.990322045829.jobaldwi@vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Mar 1999, John Baldwin wrote:
>
> On 22-Mar-99 Richard Wackerbarth wrote:
> > There is a problem with this approach.
> >
> > /etc/defaults/rc.conf defines ${rc_conf_files}
> > However, I have no chance to override it before it is used.
> >
> > However, I fear that you need a bit more logic to allow the
> > overriding of ${rc_conf_files}.
>
> Where are going to override it? If we use some other config file that gets
> sucked in to /etc/defaults/rc.conf we'd have a config file included in
> another config file that tells it what other config files to include. If this
> keeps up we'll end up with a bunch of config files floating around that config
> other config files, which will end up messy and confusing for newbies, IMHO.
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}.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9903220415270.72040-100000>