[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lzip-bug] Tarlz 0.4: Scan or Simulate feature regarding 'ustar' for

From: Antonio Diaz Diaz
Subject: Re: [Lzip-bug] Tarlz 0.4: Scan or Simulate feature regarding 'ustar' format
Date: Thu, 02 Aug 2018 01:27:08 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv: Gecko/20110420 SeaMonkey/2.0.14

Hi Timothy,

Timothy Beryl Grahek wrote:
When --scan or --simulate is called, it scans whatever folders or
files are appended after --scan or --simulate and sees if those
elements meet the requirements of the 'ustar' format.

You may achieve something like this with tarlz or with GNU tar:

$tarlz -c --uncompressed foo > /dev/null
tarlz: foo/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz: File name is too long.
tarlz: Exiting with failure status due to previous errors.

$tar -c --format=ustar foo > /dev/null
tar: foo/zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz: file name is too long (cannot be split); not dumped
tar: Exiting with failure status due to previous errors

In fact GNU tar detects when the output is /dev/null and does not read the files:

"When the archive is being created to `/dev/null', GNU tar tries to minimize input and output operations."

since it [tarlz] by default uses 'ustar' for a very good reason.

I'm determined to find or modify a tar format suitable for tarlz. But it will take some time because I'll try to develop a consensus first with other tar developers and posix. It has been a shock to discover that pax is flawed. :-(

Best regards,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]