Re: [Duplicity-talk] Tarfile support

[Rob Browning]

Ben Escoto <address@hidden> writes:

> It wouldn't be that hard now because rdiff-backup (for speed purposes,
> and to preserve metadata not supported by destination file systems)
> already has a file format for recording all the metadata.  All that
> would be left storing the data in regular files.  For that we could
> use a simple file format like:
>
> <bytes in filename> filename <bytes of data> data
> <bytes in filename> filename <bytes of data> data

Also, if we were going to have a duplicity specific format, would we
have to worry about endianness, and could/should we add some kind of
encoding (even if we don't have redundancy) that would make it
possible, to re-synchronize on the next file if data was lost?  I
guess if we're only targetting hard drives, just having sync markers
may not be helpful since you're unlikely to get shortened files.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4