Re: PROPOSAL: Services, inetd and xinetd
On Tue, Apr 28, 1998 at 11:05:35PM +0100, Mark Baker wrote:
> We have one. It's called /etc.
This is, mostly, true.
_BUT_ there is a different point about this: System
administrators should be educated to use RCS or CVS for
their configuration files, and they should _not_ edit the
production files in /etc/*. So, what is really needed is
a centralized repository which puts all configuration
filese under RCS or CVS control. A "make install" in that
directory would then put all the configuration files in
place (with correct ownership and permission). It could,
additionally, perform tasks like generating
/etc/mail/aliases.db from /etc/mail/aliases, etc.
A good example for how this can be done is INN's
sample/site concept: When first installing INN, the site
directory is populated with the sample files. When you
upgrade INN, you are told which sample files have changed;
you can then easily import the sample files or keep your
local changes.
All this is (for additional comfort) combined with RCS
version control.
Translated to Debian, this would mean that packages would
maintain the "sample" files, while users use the "site"
directory for their own stuff.
tlr
--
Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/
2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: