Date: Tue, 01 Apr 1997 14:38:19 -0700 From: "Justin T. Gibbs" <gibbs@plutotech.com> To: asami@vader.cs.berkeley.edu (Satoshi Asami) Cc: pst@shockwave.com, ache@nagual.ru, peter@freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/security/ssh/pkg PLIST Message-ID: <199704012140.OAA08296@pluto.plutotech.com> In-Reply-To: Your message of "Mon, 31 Mar 1997 22:23:11 PST." <199704010623.WAA04518@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
> * Well, anyway, can we deal with this shared /usr/local problem now since > * this topic has reared its ugly head again? > * > * I'd be fine with /usr/local/local or /var/etc or /etc or whatever. I don't > * give a darn where "local" files are kept, as long as you can share /usr/loc >al > * across multiple machines. > >This has already been discussed in the past. Setup scripts should be >kept in /usr/local/etc. If you want to share /usr/local, symlink it >to wherever you want. And then mount /usr/local/etc on top of it? How do you allow for a package that has per host configuration data to be shared if /usr/local (along with /usr/local/etc) is coming from a central server? >Satoshi -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704012140.OAA08296>