From owner-freebsd-hackers Thu Nov 28 04:47:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA24227 for hackers-outgoing; Thu, 28 Nov 1996 04:47:06 -0800 (PST) Received: from spoon.beta.com ([199.165.180.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA24222 for ; Thu, 28 Nov 1996 04:47:03 -0800 (PST) Received: from spoon.beta.com (localhost [127.0.0.1]) by spoon.beta.com (8.8.2/8.6.9) with ESMTP id HAA08015; Thu, 28 Nov 1996 07:46:33 -0500 (EST) Message-Id: <199611281246.HAA08015@spoon.beta.com> To: joerg_wunsch@uriah.heep.sax.de, hackers@freebsd.org Subject: Re: /usr/local/etc/*.d... In-reply-to: Your message of "Thu, 28 Nov 1996 10:40:13 +0100." <199611280940.KAA01121@uriah.heep.sax.de> Date: Thu, 28 Nov 1996 07:46:32 -0500 From: "Brian J. McGovern" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Your environment is a typical case where you best move out the entire >/usr/local/etc e.g. under /etc/local, and put a symlink for it there. >However, ports&packages policy is to _not_ touch parts of the base >system, so /etc/ is tabu for them. > >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) I unfortunately agree with this as well. However, as in the past I've had to tinker with /etc/rc.local to get most of this stuff up, I wouldn't be adverse to an /etc/rc.d, or some such. Also, this is not a case where the ports or packages would in and of themselves be touching the base system, but rather an option that was touched by the system administrator who would like to see these services run. Configs and what not, can, in my opinion, stay in /usr/local/etc, or be symlinked someplace in to /etc. Again, the ports/packages aren't doing the touching. I think that someplace in /etc should be reserved for startup, /usr/local (as dumb as it sounds) be retained for shared files, and perhaps another directory (/usr/reallylocal ???? :) ) be reserved for specific local configs. A good example of the "greying" of this area is the XFree config file (/etc/XF86Config). By definition, shouldn't this live someplace in /usr/X11R6? Again, just my two cents, but I'm looking at it from minimizing the impact this change will have on the mid-size to larger user (ie - one system users probably really don't have to worry about this). -Brian