Subject: Re: Proposed rc.d changes....
To: David Brownlee <firstname.lastname@example.org>
From: Giles Lean <email@example.com>
Date: 05/02/2000 08:50:15
On Mon, 1 May 2000 16:15:52 +0100 (BST) David Brownlee wrote:
> If you have a tool that can take N rc.conf.d files, put them
> into a single file, allow it to be edited and then safely split
> everything back into individual config files then you have just
> about all the functionality needed to be able to mechanically
> update or upgrade a single rc.conf, particularly if you keep a
> copy of the stock rc.conf around and have an option to list all
> changes form the default.
True, but I would point out though that dropping in files via pkg_add,
rsync, rdist, rcp, etc is easier than dropping in files and afterward
running commands. Running commands post-install is clearly possible
so this isn't conclusive.
My own preference (bias, history, whatever) is for individual files.
The first application I used that used this technique irritated me,
but I have changed my mind over the years, as I decided that a
directory is just another type of file and realised that "vi
/etc/rc.conf.d/*" works about as well as "vi /etc/rc.conf".