David wrote:
> There's a minor reason to write out ALL the perm bit data, but
There's always the 'configurable option' approach.
Someone, I doubt Linus will have any interest in it, could volunteer to
make the masks of st_mode, used when storing and recovering file
permissions, be configurable by some environment variable settings,
which default to whatever Linus provided.
But, in general, if you want a generalized backup system, git is not it.
Git skips all files whose name begins with the dot '.' character, and
anything that is not a regular file or directory. Git makes no
concessions to working adequately on file systems lacking normal inode
numbers (such as smb, fat, vfat). Git obscures the archive format a
modest amount, for pure speed and to encourage use only via appropriate
wrappers. Git is tuned for blazing speed at the operations that Linus
needs, not for trivial recovery, using the most basic tools, under harsh
circumstances.
The basic idea of using such an 'object database' (though I dislike that
term -- too high falutin vague) of files stored by their hash is a
good one. But a different core implementation is needed for backups.
I have one that I use for my own backups, but it is written in Python,
and uses MD5, one or the other of which likely disqualifies it from
further consideration by half the readers of this list.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.650.933.1373,
1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
