[ On Saturday, August 12, 2000 at 07:07:54 (-0600), Jim Bernard wrote: ]
> Subject: Re: /etc/*.conf reorg (was Re: `rc.local.conf': bad nam )
>
>   Yet another alternative would be to create /etc/local and populate it
> as needed with (optional) *.conf files, read in (if they exist) by the
> as-shipped default files in /etc.  I think I like Luke's idea better, but
> this scheme does satisfy the concerns about completely separating locally
> maintained files from vendor-supplied files.

Your idea may be better actually, though perhaps only as a suggestion to
users, not as the default in system-provided files -- it allows for
people to choose how they manage local shell-type configuration files.

What I mean by "only as a suggestion" is that the documentation could
describe this method as a solution to people who want to avoid the
troubles of merging localisations into distributed files.  I.e. it's
going to be a whole lot easier for them to merge a one-to-three line
change at the bottom (or top) of a file than it would be to merge
changes that are interspersed throughout the file and even within
lines.

Meanwhile the system, as distributed, would continue to be as simple and
clear as possible....

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>