question about 2.6.3pre2's --link-by-hash behaviour
Erik Jan Tromp
betageek at sympatico.ca
Wed Sep 22 16:13:31 GMT 2004
On Wed, 22 Sep 2004 13:21:31 +0200
Paul Slootman <paul at debian.org> wrote:
> > I had hoped to use it both for my rotating backups & for my (unofficial)
> > slackware mirror.
> Hmmm... For a slackware mirror I expect that it would be fine.
To my eyes, a mirror implies a duplicate fileset indistinguishable from the original. Having files show up with different modes & dates - due, in this case, to the sort order of the file list & the mode/date of the first file used for linking by hash - doesn't fit that scenario. Backups are even more sensitive as user.group information _must_ be retained.
> I tried downloading the patch from the web cvs, but I got this:
> Error: Unexpected output from cvs co: cvs [checkout aborted]:
> Absolute module reference invalid:
> Check whether the directory /cvsroot/CVSROOT exists and the script
> has write-access to the CVSROOT/history file if it exists. The
> script needs to place lock files in the directory the file is in as
An alternative would be to use:
Handy stuff, that.
Registered Linux User Number 140066
"Failure is not an option. (It comes bundled with Windows.)"
"If it ain't broke, overclock it."
More information about the rsync