From owner-freebsd-current@FreeBSD.ORG Sat May 29 07:51:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2657516A4CF for ; Sat, 29 May 2004 07:51:22 -0700 (PDT) Received: from parati.mdbrasil.com.br (parati.mdbrasil.com.br [200.210.70.4]) by mx1.FreeBSD.org (Postfix) with SMTP id CDF2443D41 for ; Sat, 29 May 2004 07:51:20 -0700 (PDT) (envelope-from eksffa@freebsdbrasil.com.br) Received: (qmail 84698 invoked by uid 1014); 29 May 2004 14:51:19 -0000 Received: from eksffa@freebsdbrasil.com.br by parati.mdbrasil.com.br by uid 82 with qmail-scanner-1.20 (uvscan: v4.2.40/v4363. Clear:RC:1(200.210.42.5):. Processed in 0.017601 secs); 29 May 2004 14:51:19 -0000 Received: from unknown (HELO freebsdbrasil.com.br) (200.210.42.5) by parati.mdbrasil.com.br with SMTP; 29 May 2004 11:51:19 -0300 Message-ID: <40B8A350.8000207@freebsdbrasil.com.br> Date: Sat, 29 May 2004 11:50:56 -0300 From: Patrick Tracanelli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; pt-BR; rv:1.5) Gecko/20031207 X-Accept-Language: pt-br, en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@freebsd.org Subject: /usr/local/etc/rc.conf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 May 2004 14:51:22 -0000 I remember it has been discussed before, but the terms were a little bit different, so tell me, isn't it appropriate rc.subr to suck the configuration parameters from /usr/local/etc/rc.conf instead of /etc/rc.conf when running startupscripts for third party applications (/usr/local/etc/rc.d/)? To keep the organization principles, I dislike putting those instructions into /etc/rc.conf when it should be read by 3rd party apps, since I consider /etc/ to be used by the base system. Altho' old style .sh scripts are still usefull under ${local_startup} dirs, ports maintainers tend to write new style rc scripts that uses rc.subr to read the user defined options (usually via /etc/rc.conf). Easy solution would be rc_conf_files="/etc/rc.conf /etc/rc.conf.local /usr/local/etc/rc.conf" into /etc/rc.conf, but it seems to be ignored by rc.subr when it's not at /etc/defaults/rc.conf; Some 3rd party startupscripts read rc.subr from /usr/local/etc/, so if it suck only ${PREFIX}/etc/rc.conf options, would force users to configure it in the right place, but it would break POLA and since some scripts read /etc/rc.subr instead if ${PREFIX}/etc/rc.subr, would also break some ports (very very bad idea). So, to allow ports startupscript to be configured from /usr/local/etc/rc.conf but also prevent people who are today used to mix everything in /etc/rc.conf from having their app. not starting, defining rc_conf_files="/etc/rc.conf /etc/rc.conf.local /usr/local/etc/rc.conf" into /etc/defaults/rc.conf would just do it, nothing would break and port's pkg-message could start trying to educate users to populate /usr/local/etc/rc.conf for ports startup options and leaving /etc/rc.conf only for the base system... -- Atenciosamente, Patrick Tracanelli FreeBSD Brasil LTDA. The FreeBSD pt_BR Documentation Project http://www.freebsdbrasil.com.br patrick @ freebsdbrasil.com.br "Long live Hanin Elias, Kim Deal!"