Is this what you want? Exalted Contributor. There is an update to tar in the form of a patch in the hp patch database. It may also give you the features you need such as being able to do files up to 8 GB for example.
Is this just and Upgrade for tar command? Whatever the path gtar is installed to is the path you need to use to execute it. You can replace the original tar command or have the 2 separate tar commands. Either way will work. Having said that I don't know and can't find a standard for encoding the version information so I would assume it's a hack that can't be relied on.
I can't say I've ever found a tar file that GNU tar couldn't handle that the Solaris tar could the reverse is as you know not true so in your situation I would just use gtar to extract files from any tar file you have. Regarding your question in the comments.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 9 years, 7 months ago. Active 9 years, 7 months ago. Viewed 5k times. Improve this question. Add a comment. GNU Tar provides the ability to create tar archives, as well as various other kinds of manipulation.
For example, you can use Tar on previously created archives to extract files, to store additional files, or to update or list files which were already stored. Initially, tar archives were used to store files conveniently on magnetic tape.
The name "Tar" comes from this use; it stands for t ape ar chiver. Despite the utility's name, Tar can direct its output to available devices, files, or other programs using pipes , it can even access remote devices or files as archives.
It can also be found on the GNU mirrors ; please use a mirror if possible. For information about Git access, alpha releases, patches, etc. Documentation for Tar is available online, as is documentation for most GNU software. A brief summary is available by running tar --help. Announcements about Tar and most other GNU software are made on info-gnu archive. Security reports that should not be made immediately public can be sent directly to the maintainer.
If there is no response to an urgent issue, you can escalate to the general security mailing list for advice. Development of Tar, and GNU in general, is a volunteer effort, and you can contribute. For information, please read How to help GNU. If you'd like to get involved, it's a good idea to join the discussion mailing list see above. Please see the NEWS file for detailed information. If extraction from a compressed archive fails because the corresponding compression program is not installed and the following two conditions are met, tar retries extraction using an alternative decompressor:.
See the NEWS file , for a detailed information. If tar is unable to determine archive compression format, it falls back to using archive suffix to determine it. Using --exclude-vcs handles also files used internally by Bazaar, Mercurial and Darcs. Name transformation expressions understand additional flags that control type of archive members affected by them. The flags are:. The corresponding upper-case letters negate the meaning, so that H means do not apply transformation to hard link targets.
The default is rsh , which means that transformations are applied to both regular archive members and to the targets of symbolic and hard links. With --create , selects compression algorithm basing on the suffix of the archive file name.
During archive creation, dereferences hard links and stores the files they refer to, instead of creating usual hard link members type '1'. This action allows to specify an action to be executed upon hitting a checkpoint. Any number of --checkpoint-action options can be specified, the actions will be executed in order of their appearance in the command line. See section 3. The --no-check-device option disables comparing device numbers during preparatory stage of an incremental dump.
This allows to avoid creating full dumps if the device numbers change e. The --check-device option enables comparing device numbers.
This is the default. This option is provided to undo the effect of the previous --no-check-device option, e. Any number of --transform options can be given in the command line. The specified transformations will be applied in turn.
Argument to --transform option can be a list of replace expressions, separated by a semicolon as in sed. Filename transformations are applied to symbolic link targets during both creation and extraction.
Tar 1. For a detailed description, see section 6. Previous versions always stored absolute file names in rename records, even if -P was not used. This is fixed: rename records contain file names processed in accordance with the command line settings.
When supplied an archive smaller than bytes in reading mode -x , -t , previous tar versions silently ignored it, exiting with code 0. It is fixed. Tar now issues the following diagnostic message: This does not look like a tar archive , and exits with code 2. In addition to affecting regular archive members, the --transform option affects hard and symbolic link targets and the --strip-components option affects hard link targets as well. Alpha release in preparation for next stable version.
See its announce , for the detailed description of bug fixes and new features. Unpacking archives piped from standard input now works correctly. This logic flaw was introduced in version 1. If you have already downloaded version 1.
0コメント