gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Need to version control entire root file system


From: Ben West
Subject: Re: [Gnu-arch-users] Need to version control entire root file system
Date: Mon, 28 Jan 2008 09:07:21 -0700

Hypothetically, you could mount another file system over root using union-fs and see that the arch meta-data lived in the mounted version instead of the original (e.g. the arch meta-files would exist in a ghost directory somewhere, pehaps, less visible to the system.

you would mount root as usual
in a subdirectroy, you would remount root (readonly)
then mount another arch-metadata directory over top (writeable)
so that any changes to the metadata would be written to the seocnd directory -- then for updates/syncs, etc you would sync/update the union file system

I'd consider reading up on unionfs to see if this will work for you. 


Also, I think the latest version of reiser supports version control build in.

On Jun 22, 2007 10:18 AM, Worley, Chris B <address@hidden> wrote:
Not user's home directories, but everything else; and no version control
meta-data cruft left lying around inside my image.

The base "image" is kept offline.  I want to version control changes to
every file and directory in that offline image.

Ascii files need explicit diffs, binary files can just be flagged as
changed.  I need to be able to view which files changed at any check-in
point, what files are different now from the last check-in, how the
ASCII files changed between any two versions, and roll-back the entire
image to any previous version.

Mostly, I need the diff repository to be outside the image; I don't want
hidden version control directories in every directory of my file
system... I need the version control meta-data kept elsewhere (this
image gets provisioned onto systems).

Will Arch do this?  If not, can anybody recommend a good version control
utility (or maybe one that is extensible) for this?

Note that I use "image" to mean "root file system", and not a disk image
per se; something you could chroot to.

Thanks,

Chris


_______________________________________________
Gnu-arch-users mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]