Date: Thu, 31 Aug 2006 10:03:19 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: ru@freebsd.org Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, gad@freebsd.org Subject: Re: "Chatty" config files in /etc Message-ID: <20060831.100319.756907628.imp@bsdimp.com> In-Reply-To: <20060831100004.GB52914@rambler-co.ru> References: <20060830202834.GA11284@rambler-co.ru> <p0623091dc11bbf999504@[128.113.24.47]> <20060831100004.GB52914@rambler-co.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20060831100004.GB52914@rambler-co.ru>
Ruslan Ermilov <ru@FreeBSD.org> writes:
: > b) by putting them in /etc/defaults, users do *see* the changes
: > when they run mergemaster, even though they won't have to
: > merge those changes with local changes. In some cases the
: > changes to the comments or examples will suggest some change
: > that the user should be making to their own already-working
: > configuration, even though their configuration won't match
: > the default system-config. I'm thinking when some comment
: > is added like:
: > # NOTE: Please see pf.conf(5) BUGS section before
: > # using user/group rules.
: >
: No, /etc/defaults are different beasties -- they are true
: default config files -- they are either used if there's no
: corresponding version under /etc, or most likely sourced
: to provide defaults. To be moved to /etc/defaults, a file
: should gain the same property.
Agreed. We've done this with all the other ones...
I'd be real careful about doing it to /etc/hosts, however, as there
are a large number of tools that munge it that might break if this is
done badly...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060831.100319.756907628.imp>