Well, looking at the archives for the SVN user lists, I came across this
from the v1.0 announcement of FSVS:
FSVS is a backup/archival-tool, which uses subversion backends for
storage. It stores the most needed meta-data, ie. owner, group,
access mode, and modification time. So versioning of /etc (or the
whole installation) is now easier, and a retrieval can restore the
access rights, too.
Due to the usage of subversion repositories as storage space all
previously committed versions of the files are available in case of
hardware problems, data loss, virus infections, user problems etc.
FSVS runs currently only on linux.
So the answer to #1 is that, yes, FSVS simply uses the same backend as
SubVersion. Which means that I can connect it directly to our existing
SVN repositories.
And some more background information from the v1.0.5 release thread,
which might be useful to add to the FSVS site. (This is the sort of
information that catches my eye when I'm trying to figure out what a
particular piece of software does.)
The differences between the svn client and fsvs are:
- fsvs keeps the modification timestamp, the owner, group and access
mode of your files in the repository, and restores them on
update/export.
- svn is restricted to files, directories, and symlinks; fsvs does
device nodes too.
- The svn client needs the .svn-directories, with the full-text of
your text-base in them; that means 4x the inodes, and >2x the space
needed in your filesystem.
Because of that is FSVS faster (at least IMO, I didn't benchmark it
against svn); it's sometimes faster than a find, because it has the
nodes sorted by inode in it's datafile, and so can drive the disk in
a nearly linear fashion, whereas svn fetches information for *many*
files, which pollute the file and inode cache, ...
- There is some resistance in svn against including full-meta-data
versioning; the arguments are code bloat and maintenance.
Point #1 in that description raises a question... and maybe this is a
foolish question. How well does that play with SELinux (i.e. CentOS5)
in enforcing mode? (Yes, I need to read up on exactly how SELinux does
it's magic, it's still a black box for me that is *mostly* just working.)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
