On Apr 15, 2005, at 10:20 AM, Neil Schneider wrote:
If someone wants to volunteer to set up CVS for all the configuration files that would be fine with me. For me it's really too much work, I just want some kind of simple revision control for the few changes to files in /etc that different people make. A full blown CVS server isn't necessary. However if someone like Stewart volunteers to set it up and load all the changes already in RCS into it, I'll use it. If it can be automated, so much the bettter.
I didn't suggest creating a full-blown CVS server:
#mkdir /var/cvs #export CVSROOT=/var/cvs #cvs init #cd /etc #cvs import -m "Initial /etc import" etc andrewl REL_0_0
Don't quote me on this, but it should be pretty damn close to that simple if sparky already has CVS.
#cd /etc ##System will pick up CVSROOT from the CVS directory #vi hosts #<make changes> #cvs commit
And most of us are probably using editors that already automate most of that.
So how is this more work than RCS? In addition, you get the advantage that your repository can be placed on a different disk from your configuration directory so that they don't both die simultaneously.
BTW, there's nothing in /etc/RCS to import into CVS? Am I missing something?
-a
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
