[rdiff-backup-users] Re: new windows version

[Chinook]

Dave Kempe wrote:

> Hi,
> fsyncing problems notwithstanding, rdiff-backup for windows 1.0.1 is 
> now available.
> it seems to work as well as the last versions :)
>
> http://solutionsfirst.com.au/~dave/backup/rdiff-backup1.0.1w4.exe
>
> let me know if there are any fixes needed.
> I did see someone had written a cool batch file that did useful stuff 
> - I can't find it here, but if anyone wants to add anything to this 
> package, let me know.
>
> thanks
>
> dave
>
>
> _______________________________________________
> rdiff-backup-users mailing list at address@hidden
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: 
> http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Dave,

I won't comment on Windows as there isn't anything a Mac convert can say 
that others want to hear :-)

However, I did post on 9/18 about EAs and ACLs on OS X (10.4.2).  In 
trying to help, Ben mentioned that I might contact the authors of 
pyxattr and pylibacl.  The answers one gets are the same as on the rsync 
list - "You'll have to contact Apple about their handiwork."

I've since got waylaid on an ObjC task, but at the time I noted that I 
have Apple's version of "xattr" as well as Apple's Carbon ACL modules.  
In the ACL modules it specifically notes that some are non-portable.   
Do you have any intention/leaning towards testing for the OS and using 
the appropriate imports and methods applicable?

Also (and you don't have to answer as I'll get back to RTFM and studying 
the source) I noticed a post today about bootability.  I was thinking 
(hoping :-) of creating a volume clone with "asr" and using rdiff-backup 
against such.  This in lieu  of  rsync  and fancy  
incrementals/snapshotting.   Am I in outer space again?

Thanks,
Lee C