Date: Mon, 9 May 2011 10:32:18 -0700 From: Gordon Tetlow <gordon@tetlows.org> To: Devin Teske <dteske@vicor.com> Cc: freebsd-rc@freebsd.org Subject: Re: [RFC][Change-Request] Create usefulness in rc.subr etc/rc.conf.d/*.conf namespace. Message-ID: <BANLkTimqhu215ZdHwx=fHqu33NXj2pYpvw@mail.gmail.com> In-Reply-To: <01d201cc0e6c$47d4b180$d77e1480$@vicor.com> References: <20110508191336.GC3527@DataIX.net> <BANLkTi=hozQBLUC15NsF2rky2OfFW=t_RQ@mail.gmail.com> <01d201cc0e6c$47d4b180$d77e1480$@vicor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 9, 2011 at 10:12 AM, Devin Teske <dteske@vicor.com> wrote:
> The solution is to have a script that can tell you these two details:
>
> 1. What is the final value of ``*_enable''
> 2. Which file assigns said final value
>
> If you have those two pieces of information, then unraveling a twisted
> configuration is easier.
>
> [Re-]welcome my sysrc(8) script:
While this is a very cool script, I have to wonder how far we have
strayed if we require another tool to tell us how the system is
configured. Surely we should be aiming for simplicity in our
implementation and not something incredibly complex.
After Jason's proposal, we would have the following list of configuration files:
/etc/defaults/rc.conf
/etc/rc.conf
/etc/rc.conf.local
/etc/rc.conf.d/{name}
/etc/rc.conf.d/*.conf
Personally, I think this is too many.
Regards,
Gordon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimqhu215ZdHwx=fHqu33NXj2pYpvw>