Thomas <[EMAIL PROTECTED]> wrote: > well, I try it in short words: volume headers of gnu tar are > considered to have a filesize of 0 bytes (that means no data appended > to the header). Ok, so it works on extracting - the size is setup to 0 > bytes, but if I list/test the archive, gnu tar trust on the size found > in the header. some listings to explain/show: Fcc: sent-messages > > $ tar -tf abc.tar # ok, no danger? > abc/not-a-file.gif > abc/CCC
Any hints on how to reproduce this behavior? Regards, Sergey _______________________________________________ Bug-tar mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-tar
