Version control for /etc
Last year I tried using RCS to do a version control of a server’s /etc direcotry. That didn’t work out too well, because the extra copies of every archive turned out to cause errors for some applications. Also it was very cumbersome to use, because you have to manually add every archive and use ‘co’ every time before editing. So I’d much rather use something like Subversion or darcs. Especially darcs because it doesn’t create a separate control directory for every directory unter version control (CVS creates a directory called “CVS” everywhere, Subversion one called “.svn” and darcs just creates “_darcs” in the top level directory. Today for the new server at the Diego Thomson I did some experiments with Subversion. This went from “cool” to “oh now” to “cool” to “oh now” now. But let me extend on this story. First I thought, well this would be very cool. Also because most applications will ignore the hidden folder (".svn") while having problems with visible folders (“CVS”) this should work. And: subversion stores symlinks without problems. Then I realized that it doesn’t store file permissions and was demoralized by this. A Yahoo! search then turned up the Subversion FAQ, specifically the entry How can I do an in-place ‘import’. ...