Subject: Re: `rc.local.conf': bad name
To: Simon Burge <simonb@NetBSD.ORG>
From: Todd Vierling <firstname.lastname@example.org>
Date: 08/01/2000 11:12:58
On Wed, 2 Aug 2000, Simon Burge wrote:
: I am partial to the *.conf thing myself. One idea is to rename the
: existing /etc/rc.conf to /etc/rc.defaults and having that source
This could be usable. However, we'll need to create a template `rc.conf'
that is blank to go with this, so that users know the difference. We'll
need to change text describing the use of rc.conf vs. rc.defaults, in
sysinst and install notes.
The problem with `rc.local.conf' is that, assuming `*.conf' are config
files, this filename tends to suggest that it's a config file for rc.local,
which it is not. That's confusing.
What I'd really like to do is use _some_ other name besides `rc.local.conf',
and include a textual comment at the top of rc.conf describing the add-on
file and what its purpose is. Some people may prefer the method of just
editing rc.conf; the hook for the additional file is for people (like me)
who like the idea of a machine-specific file with minimal settings.
That concept of add-on files suggests the name `rc.conf.local', in the vein
of `weekly.local', `netstart.local', and even `rc.local', and I can't think
of another sane name to use. <sigh>
-- Todd Vierling <email@example.com> * http://www.wasabisystems.com/
-- Speed, stability, security, and support. Wasabi NetBSD: Run with it.