From owner-freebsd-ports@FreeBSD.ORG Thu Feb 19 14:11:07 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49AA716A4CF; Thu, 19 Feb 2004 14:11:07 -0800 (PST) Received: from enterprise.sd73.bc.ca (romulus-net.sd73.bc.ca [142.24.13.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB90B43D1F; Thu, 19 Feb 2004 14:11:06 -0800 (PST) (envelope-from fcash-ml@sd73.bc.ca) Received: from mailtest.sd73.bc.ca (mailtest.sd73.bc.ca [10.10.10.14]) i1JM2p7O015729; Thu, 19 Feb 2004 14:02:51 -0800 Received: from 207.23.164.8 (SquirrelMail authenticated user fcash) by mailtest.sd73.bc.ca with HTTP; Thu, 19 Feb 2004 14:11:04 -0800 (PST) Message-ID: <49331.207.23.164.8.1077228664.squirrel@mailtest.sd73.bc.ca> In-Reply-To: <87y8qywx47.fsf@gray.impulse.net> References: <87u11p8sl6.fsf@gray.impulse.net><20040218180829.B43291@carver.gumbysoft.com><001401c3f732$93405c40$c700a8c0@lxfvm8jmsx9muk3> <87y8qywx47.fsf@gray.impulse.net> Date: Thu, 19 Feb 2004 14:11:04 -0800 (PST) From: "Freddie Cash" To: ports@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-RAVMilter-Version: 8.4.1(snapshot 20020919) (enterprise.sd73.bc.ca) cc: current@freebsd.org Subject: Re: Feature Request: /usr/local/etc/rc.conf support X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 22:11:07 -0000 Just curious why everyone is trying to come up with such complex solutions to this issue. Everything else is split along the lines of base <---> ports. Why should this be any different?? There's an etc/ directory for the base system, and an etc/ directory for the ports. The beauty of this system is that ports don't muck around in the base system (with the exception of the few that support and override_base option). It's really annoying to have to keep changing between /usr/local/etc/ to edit configuration files, and /etc/ to enable daemons that are started by scripts in /usr/local/etc/rc.d/. There's an rc.conf for the base system, why not an rc.conf for the ports? Why does a port have to modify anything in the base system's etc/? There should either be separate etc/ directories, separate rc.conf files, separate rc.d/ directories for ports and base, or there should be two separate /etc/rc.conf files: 1 for listing daemons to start, the other for listing system variables that should only change at boot time (like securelevel, network settings, and so on). -- Freddie Cash fcash-ml@sd73.bc.ca