From owner-freebsd-current Tue Feb 9 14:58:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21297 for freebsd-current-outgoing; Tue, 9 Feb 1999 14:58:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21281 for ; Tue, 9 Feb 1999 14:58:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.2) with ESMTP id OAA24601; Tue, 9 Feb 1999 14:58:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon cc: David Wolfskill , current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. In-reply-to: Your message of "Tue, 09 Feb 1999 14:57:50 PST." <199902092257.OAA61537@apollo.backplane.com> Date: Tue, 09 Feb 1999 14:58:39 -0800 Message-ID: <24597.918601119@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want to put 'read only' junk into /etc/defaults, then why aren't > you also sticking /etc/rc, /etc/rc.network, /etc/rc.firewall, etc etc etc > into /etc/defaults ? It makes no sense to have an /etc/defaults/ > directory if you are still mixing read-only and user-modifiable files > in /etc. There is an eventual plan to put more things into /etc/defaults, yes. One has to, however, start somewhere. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message