Re: version control for config files
Ralf Gesel|ensetter wrote:
If you are talking of config files which reside in the etc
directory this
Mh, not all are in /etc, some are on tjener, most are on work
stations (we only got one luckywise) and on the LTSP server. We could
start a collection of questionable conf files....
As far as I know...
[ Dear experts, please correct me where i'm wrong :) ]
*All* config files for the system reside _physically_ in /etc;
this is debian policy (or isn't it?).
(If a program expect the conf-file in some other dir, then the
file is in /etc an a symlink to /etc is at the expected place.)
So you can make a tar just from /etc without special options [e.g. for
symlinks] and have all the system config in one tarball.
(You can't do that this simple with e.g. a standard SUSE system.)
LTSP config files that contain settings (X, mouse, swap, sound, ...) for
the _client_ reside in /opt/ltsp/..., which makes sense because there is
the the whole system [including / and /etc] for the _thin-clients_
[...and _not_ for the ltsp host server itself].
(Don't have an LTSP here to give exact paths.)
Furthermore we dont have to make up a collection of conf-files,
because every conf-file in the system is known as such by the debian
package management system.
(Every .deb-package 'says' which of the files that come with it are
conf-files.)
I think one just needs a mechanism to watch files for changes
(e.g. "fam" does that) and initiate a cvs commit when that happens.
And some tool which gets the conf-file information (see above) from
the package management system and makes up a configuration for "fam"
out of it.
Best wishes,
Patrick
Reply to: