:> 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
<[email protected]>
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
