If the kickstart files are in /etc, then you can use etckeeper. It wraps git (by default - it could use mercurial, bazaar or darcs instead). You'd only have to issue git commands if you want to recover files. (Hmm, it looks like you can tell etckeeper to work on a different directory than /etc if you want to.) Plus it will save all your files in /etc the same way, not just the kickstart files. Your use case is exactly what etckeeper is for. Just one repo, local to the machine (no distributed servers to push to or pull from). The package manager has hooks to etckeeper, and whenever you upgrade your machine etckeeper will take a snapshot of your /etc directory. bjb On Tue, Dec 13, 2011 at 12:28:07AM -0500, Peter Sjoberg wrote: > I have a kickstart env with a pile of scripts and a few configfiles (for > server info like ips, disk layout...). To keep track of the changes I > been using cvs but I'm now about to an overhaul of it and wonder if cvs > is the best tool for it. > > * The env is all on one server and in one location (no user dev areas or > so) > * OS is redhat 6. pref if it's included but not a must > * only check-in on same server, checkout to same server when something > got screwed up. > must be extremely simple to use > cvs commit -m"added new static route" STD_GATEWAY > is about as complicated as it can be. > > I was about to take a look at cvs,svn,git,rsync and so on but figured I > can ask here where people actually use them and can give first hand > experiance. > > /ps > > _______________________________________________ > Linux mailing list > Linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca > http://oclug.on.ca/mailman/listinfo/linux ---end quoted text---