From owner-freebsd-current Mon Mar 22 12:55:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mx4.dynasty.net (mail.dynasty.net [208.200.172.236]) by hub.freebsd.org (Postfix) with ESMTP id 4D74F15256 for ; Mon, 22 Mar 1999 12:55:14 -0800 (PST) (envelope-from cpinckard@dynasty.net) Received: from dynasty.net ([12.14.196.151]) by mx4.dynasty.net (Netscape Messaging Server 3.52) with ESMTP id 194; Mon, 22 Mar 1999 14:53:59 -0600 Message-ID: <36F6AB15.48DFD933@dynasty.net> Date: Mon, 22 Mar 1999 14:41:57 -0600 From: Chas X-Mailer: Mozilla 4.04 [en] (Win95; U) MIME-Version: 1.0 To: paul@originative.co.uk Cc: rkw@dataplex.net, current@freebsd.org Subject: Re: /etc/rc.conf, take 46! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that sounz like a simple solution.:)) Paul... > > Unless someone comes up with a scheme that tracks set membership and > > allows us to add to that set, I think that we should stick to > > the "simple" > > approach. > > > > /etc/defaults/rc.conf defines ${rc_conf_files} to be "/etc/rc.conf" > > > > /etc/rc.conf is allowed to override this definition to > > include additional > > files such as "/etc/rc.conf.local" > > > > Those files get sucked in. > > > > - - - > > > > An alternate, and perhaps cleaner approach would be to always suck in > > /etc/defaults/rc.conf and /etc/rc.conf. Then suck in those > > files specified > > in ${additional_rc_conf_files}. > > I still think we're chasing our tails with all this configuration stuff. > > Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if > present). Don't have anything in /etc/defaults.rc.conf except default > variable settings. > > The local admin can do what the hell they want in /etc/rc.conf, including > putting in a bit of script to load /etc/rc.conf.local > /etc/rc.conf.flavour_of_month etc. > > Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message