Date: Thu, 27 Aug 1998 10:20:00 +0100 From: nik@iii.co.uk To: Satoshi Asami <asami@FreeBSD.org> Cc: dillon@backplane.com, jkoshy@FreeBSD.org, bde@zeta.org.au, committers@hub.freebsd.org Subject: Re: cvs commit: src/etc make.conf Message-ID: <19980827102000.I6112@iii.co.uk> In-Reply-To: <199808270911.CAA11793@silvia.hip.berkeley.edu>; from Satoshi Asami on Thu, Aug 27, 1998 at 02:11:04AM -0700 References: <19980827100624.G6112@iii.co.uk> <199808270911.CAA11793@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 27, 1998 at 02:11:04AM -0700, Satoshi Asami wrote:
> * I like /etc being as static as possible. It minimises the amount of
> * work I have to do when I upgrade the system (since most of my changes
> * are in /usr/local/etc) and it's a step in the right direction to being
> * able to mount /etc read-only.
>
> Then put it in /var/etc or whatever. That *does* *not* *belong* *to*
> *${PREFIX}*. (Sorry for shouting, but this is ridiculous.)
It's got nothing to do with ${PREFIX}, and I don't see where you got that
impression. The fact that (should something like this ever get
implemented) ${PREFIX} and kern.local_config *might* happen to have the
same value is completely irrelevant.
The FreeBSD administrator could chose to set kern.local_config to
/usr/local/etc, /var/etc, /usr/host/etc (which is a scheme I've seen people
use when /usr/local was NFS mounted), /opt/etc, or whatever, completely
seperate from whatever value is in ${PREFIX}.
N
--
--+==[ Nik Clayton becomes Just Another Perl Contractor in 16 days. ]==+--
She's still dead. Deal with it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980827102000.I6112>