Date: Tue, 9 Feb 1999 14:57:50 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: David Wolfskill <dhw@whistle.com>, current@FreeBSD.ORG Subject: Re: Heads up! /etc/rc.conf.site is dead. Message-ID: <199902092257.OAA61537@apollo.backplane.com> References: <24519.918600749@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:> Now we have /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local.
:> Considerably less simple and quite unobvious.
:
:Until you have to upgrade to the latest set of "knobs"; that problem
:is something I think people are not focusing sufficiently on in
:commenting only on the downsides of this.
:
:- Jordan
/etc/rc.conf - no touchee
/etc/rc.conf.local - touchees
People are still stuck in the 'I want to edit /etc/rc.conf' mode of
thinking.
I say that if you intend to put the /etc/rc.* scripts in /etc, and
make them read-only ( /etc/rc, /etc/rc.network, /etc/rc.firewall, etc... )
then /etc/rc.conf should stay where it is and also be read-only.
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.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902092257.OAA61537>