(For example,
my tar supports files larger than 8GB, which I was
somewhat surprised to find GNU tar didn't [...])
Recent versions at least do;
I wrote some which were around 14GB a
few weeks ago and they read back and verified against original data
OK (no errors, missing files etc.)
I don't mean archives >8G (which is what it sounds as though you're
talking about); I mean individual files >8G in the archives.
It's one of the things I dislike about tar in
general though; I'm
never sure when I'm going to hit either file size or file path length
limits.
That's why my tar uses private header formats to transparently handle
path length limits (on which it imposes no restrictions except
available memory, I think) and file size limits (on which it does
impose a 2^88-byte limit; I could lift even that limit with a little
work if I were convinced it were worth it, though I'd be unable to test
it as I have no OSes which support file sizes over 2^64). I think GNU
tar does something similar for pathname length limits.
Other than that though it's generally better than
the alternatives in
that the format's documented well
It is? Where? I've been looking for a long time for documentation on
tar format, and so far all the pointers I've found have ended up at
pay-for-play "standards". I'd love to get hold of a real spec for the
tar header block format.
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B