From owner-freebsd-stable Tue Oct 14 18:36:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA03619 for stable-outgoing; Tue, 14 Oct 1997 18:36:52 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA03613 for ; Tue, 14 Oct 1997 18:36:47 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00769; Wed, 15 Oct 1997 11:03:12 +0930 (CST) Message-Id: <199710150133.LAA00769@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: chad@dcfinc.com cc: danny@panda.hilink.com.au (Daniel O'Callaghan), Studded@dal.net, freebsd-stable@FreeBSD.ORG Subject: Re: Problem with rc.conf/rc.firewall In-reply-to: Your message of "Tue, 14 Oct 1997 10:49:59 MST." <199710141750.KAA18258@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Oct 1997 11:03:12 +0930 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm more comfortable with multiple rc. files and a master that > runs them. This may be due to more than a decade with SysV, and its > /etc/init.d setup, but it makes more sense and I find it easier to > administer system startup in byte-sized chunks. It also means packages > can be added without performing a merge into a main file (put 'em in > /usr/local/etc/rc.d). rc.conf is *NOT* used by installable packages, and never will be. It is intended to be the single repository of standard system configuration information. In some cases, the parameters that it contains may be relevant to more than one section of the system, so this is the only approach that makes sense. mike