I have used CVS for/etc of my linux boxes since 2000. It works very well. It can manage most of your change history for/etc and make them recoverable. It can even help you with ``cvs diff'' when your/etc is compromised by crackers.
One annoying point of CVS for/etc is its invasive architecture. It always creates CVS/{Entires,Root,Repository}. This affects some app, so you need to teach CVS not to handle some files/directories.
If you use non-invasive revision-control system (like SVK), such problem might be avoidable. But I have not enough experience with it yet. ---- If you feel my english is strange, please correct me!
Slashdot Mirror
Why not CVS?
/etc of my linux boxes since 2000. It works very well. /etc and make them recoverable. /etc is compromised by crackers.
/etc is its invasive architecture.
I have used CVS for
It can manage most of your change history for
It can even help you with ``cvs diff'' when your
One annoying point of CVS for
It always creates CVS/{Entires,Root,Repository}. This affects some app, so you
need to teach CVS not to handle some files/directories.
If you use non-invasive revision-control system (like SVK),
such problem might be avoidable. But I have not enough experience with it yet.
----
If you feel my english is strange, please correct me!