Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


Is there a good solution out there for revision control on an entire file system? This includes the question "would any of the typical revision control systems out there work for this (git, svn, bzr, etc.)?"

Use case:

We have filesystem images that represent installs that happen to some of our embedded systems where every last file installed can make a difference. They often require modification in the course of development, debugging, and maintenance. Those changes need to be stored along with who made them, why, and when. We also need to be able to diff the changes, and restore to particular versions.

Revisioning filesystems would sound like a good solution, but likely excluded since they include the history in the file system, the size of which we wouldn't want on our embedded systems, along with the fact that we wouldn't want the revision information ending up on a production machine. Though perhaps there's a solution to get around these problems.

share|improve this question

closed as off topic by Chris S Jun 18 '12 at 17:26

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

I asked this on SO a while back:… – MikeyB Jun 18 '12 at 17:25
We can't close as a dupe across sites, so I'm closing it as OT as the next closest thing. – Chris S Jun 18 '12 at 17:27