Re: hdup 2.0.1 argggg

[On 17 Nov, @ 21:38, Boris wrote in "Re: [hdup-user] hdup 2.0.1 arg ..."]
> Ie, if I move /opt to /foo, then /foo/fileX ought to be backed up on the
> next run even though it may not have been modified for a year.  I don't
> know of a way to catch this without keeping a list of what files were
> backed up "last time".  If pax doesn't have that ability, you may want
> to implement it within hdup.

correct me if I'm wrong, but I think you can catch this with time
based backups. Although you are forced to treat directories different
then files, but I'm already doing that.

If you move /opt to /foo the ctime changes - at least under Linux.
(if you put something in a dir the mtime changes). So when you
recursively walk a tree and encounter such a directory - you must
backup the entire subtree, no matter what. This is a bit like the
opposite of the .nobackup keyword.

So *I think* backing up isn't the problem here, how does this work
when you restore? IIRC tar doesn't delete such intermediate (in this
case /opt) directory, or does it? At least hdup cannot do this,
because I don't feed tar the listed-incremental file...

grtz Miek


PS 
on a side note: for those that understand, Reiserfs does NOT support
d_type in directory entries - making it impossible to see if something
is a file or not. The portable way to handle this is to stat each file
and dir, but this is slow - and by doing 'stat' you change one of the
c/m/a times, so you have to reset those. So, this basicly sucks...