Date: Mon, 22 Mar 1999 17:39:31 -0000 From: paul@originative.co.uk To: rkw@dataplex.net Cc: current@freebsd.org Subject: RE: /etc/rc.conf, take 46! Message-ID: <A6D02246E1ABD2119F5200C0F0303D10FE75@octopus>
next in thread | raw e-mail | index | archive | help
> -----Original Message-----
> From: Richard Wackerbarth [mailto:rkw@dataplex.net]
> Sent: 22 March 1999 10:23
> To: John Baldwin
> Cc: current@FreeBSD.ORG; Jordan K. Hubbard
> Subject: Re: /etc/rc.conf, take 46!
>
>
> 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}.
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 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?A6D02246E1ABD2119F5200C0F0303D10FE75>