Well, the tomsrtbt pax == tar == cpio program supports all of the stuff in
standard normal historical Unix tar. The Gnu-Tar has many extensions and
quirks, it is of course popular on Linux, and I guess Amanda requires
gnu-tar and the associated extensions. I think there is a gnu-tar for
libc5 in the tomsrtbt add-ons directory, if you want that. It is easy to
tell from the gnu-tar man page what features are "extra" non-compatible
options. But since it is under Amanda's control, I dunno how well
documented Amanda's use of those features is, since I don't use Amanda. I
would just get gnu-tar. -Tom
On Mon, 27 Aug 2001, John W. Price wrote:
> Date: Mon, 27 Aug 2001 13:49:33 -0700
> From: John W. Price <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [tomsrtbt] questions about tar
>
> Hi all:
>
> What are the differences between tar on tomsrtbt and gnutar? If I'm
> reading the FAQ list correctly, the main one that I should notice is the
> lack of a -z flag. From the FAQ list:
>
> =====
> tar and cpio are 'pax' and differ from gnu-tar and gnu-cpio.
>
> Instead of:
> tar -xvzf /dev/st0
> Use this:
> gzip -d < /dev/st0 | tar -xvf -
> =====
>
> When I restore a backup tar archive using the amanda system, tar doesn't
> seem to understand the output. Under tomsrtbt, I get the following:
>
> # tar -xvf hda1.0
> Tar: blocksize = 20
> tar: 07342473570/./: Unknown filetype
> tar: 07342473570/./lost+found/: Unknown filetype
> tar: 07342472621/./System.map: File exists
>
> and so on. It manages to restore some of the files (apparently; I
> haven't probed too deeply yet), but most of them get skipped for some
> reason or another.
>
> The archive was created by amanda using gnutar, if that helps.
>
> John
