On 2008/02/14 10:26, Darrin Chandler wrote: > On Thu, Feb 14, 2008 at 05:02:02PM +0000, Richard Wilson wrote: > > Before I embark on this, I have a couple of questions: > > > > 1) Can anyone think of an idea why I'm being dumb? I hope not, but it > > doesn't hurt to ask. > > Many, many people store configs in cvs. It's a good idea. > > > 2) How will /etc, and the things that read it, react to /etc becoming a > > working copy, with CVS, Entries, et al? I'm thinking of things that eg > > "Include /etc/appname/*" barfing on unexpected files left by CVS. > > One technique is to do cvs from another directory completely, with > symlinks to the files you're interested in. I.e. ~/configs/etc or > /var/configs/etc or ... > > That keeps /etc clean, but requires you to have the discipline to > symlink the files you change. > > I'd be interested to read of different ways.
I push the files from a machine which contains checkouts as a "configuration master". (I just use scp, but there are of course many other options). I use one directory per host, and template directories for groups of hosts, all checked-in to CVS. There are other ways to handle this, some people use cfengine or puppet. I haven't got sufficiently annoyed with my cobbled- together scripts to work out how to use another method yet. Take care of file permissions, some software will refuse to read config if permissions are too loose. You wouldn't want to discover this at reboot time (-:
