Archive Name And Parameters Meaning
The Linux “tar” stands for tape archive, which is used by large number of Linux/Unix system administrators to deal with tape drives backup. The tar command used to rip a collection of files and directories into highly compressed archive file commonly called tarball or tar, gzip and bzip in Linux.The tar is most widely used command to create compressed archive files and that can be moved. What Is an Archive File Used For? A backup software program, or the software tool your online backup service has you install on your computer, can use a few different methods to help determine if a file should be backed up, such as looking at the date at which it was created or modified.
SYNOPSIS
unzip [
DESCRIPTION
unzip will list, test, or extract files from a ZIP archive, commonly found on MS-DOS systems. The default behavior (with no options) is to extract into the current directory (and subdirectories below it) all files from the specified ZIP archive. A companion program, zip, creates ZIP archives; both programs are compatible with archives created by PKWARE's PKZIP and PKUNZIP for MS-DOS, but in many cases the program options or default behaviors differ.
If the archive contains Unix or Win32 symbolic links, these will be displayed (a 0x80000 in the non-MSDOS external file attributes field with both Unix/Linux/MacOS and PTC MKS Toolkit) or restored to NTFS volumes to point to the same names (existing or not existing) as they were in the source file system. Where the source is on an NTFS volume and target does not exist, a file symbolic link will be created.
Options
zipinfo mode. If the first option on the command line is
[OS/2, Unix (but not PTC MKS Toolkit) DLL] print extended help for the DLL's programming interface (API).
extract files to stdout/screen (``CRT'). This option is similar to the
freshen existing files, i.e., extract only those files that already exist on disk and that are newer than the disk copies. By default unzip queries before overwriting, but the
list archive files (short format). The names, uncompressed file sizes and modification dates and times of the specified files are printed, along with totals for all files specified. If UnZip was compiled with OS2_EAS defined, the
list zipfile information in verbose, multi-page format.
extract files to pipe (stdout). Nothing but the file data is sent to stdout, and the files are always extracted in binary format, just as they are stored (no conversions).
test archive files. This option extracts each specified file in memory and compares the CRC (cyclic redundancy check, an enhanced checksum) of the expanded file with the original file's stored CRC value.
[most OSes] set the timestamp on the archive(s) to that of the newest file in each one. This corresponds to zip's
update existing files and create new ones if needed. This option performs the same function as the
list archive files (verbose format) or show diagnostic version info. This option has evolved and now behaves as both an option and a modifier. As an option it has two purposes: when a zipfile is specified with no other options,
display only the archive comment.
Modifiers
convert text files. Ordinarily all files are extracted exactly as they are stored (as ``binary' files). The
treat all files as binary (no text conversions). This is a shortcut for
[when compiled with UNIXBACKUP defined (as it is with PTC MKS Toolkit)] save a backup copy of each overwritten file. The backup file is gets the name of the target file with a tilde and optionally a unique sequence number (up to 5 digits) appended. The sequence number is applied whenever another file with the original name plus tilde already exists. When used together with the 'overwrite all' option
Cosmotheism is the religion of European Civilization. William luther pierce hunter pdf. Cosmotheism is the religion of reality and science. Cosmotheism is the religion that will change your life forever.Watch our free videos here: Cosmotheism is the Meaning of Life, The Path, On Living Things, and On Society to begin your quest. Cosmotheism is the religion of God — the real God, whose true words are mathematics, physics, and genetics.
Example: the old copy of ``foo' is renamed to ``foo~'.
Warning: Users should be aware that the
use case-insensitive matching for the selection of archive entries from the command-line list of extract selection patterns. unzip's philosophy is ``you get what you ask for' (this is also responsible for the
Please note that the
skip restoration of timestamps for extracted items. Normally, unzip tries to restore all meta-information for extracted items that are supplied in the Zip archive (and do not require privileges or impose a security risk). By specifying
On VMS, the default setting for this option is
[MacOS only] display contents of MacOS extra field during restore operation
[non-Acorn systems supporting long filenames with embedded commas, and only if compiled with ACORN_FTYPE_NFS defined (which PTC MKS Toolkit does not)] translate filetype information from ACORN RISC OS extra field blocks into a NFS filetype extension and append it to the names of the extracted files. (When the stored filename appears to already have an appended NFS filetype extension, it is replaced by the info from the extra field.
[MacOS only] ignore filenames stored in MacOS extra fields. Instead, the most compatible filename stored in the generic part of the entry's header is used.
junk paths. The archive's directory structure is not recreated; all files are deposited in the extraction directory (by default, the current one).
[MacOS only] ignore MacOS extra fields. All Macintosh specific info is skipped. Embedded control characters in file names might have nasty side effects when displayed on screen by some listing code without sufficient filtering. And, for ordinary users, it may be difficult to handle such file names (e.g. when trying to specify it for open, copy, move, or delete operations). Therefore, unzip applies a filter by default that removes potentially dangerous control characters from the extracted file names. The
[VMS] force unconditionally conversion of file names to ODS2-compatible names. The default is to exploit the destination file system, preserving case and extended file name characters on an ODS5 destination file system; and applying the ODS2-compatibility file name filtering on an ODS2 destination file system.
ENVIRONMENT
unzip's default behavior may be modified via options placed in an environment variable. This can be done with any option, but it is probably most useful with the
Unix (and PTC MKS Toolkit) Bourne shell:
Unix (and PTC MKS Toolkit) C shell:
OS/2 or MS-DOS:
VMS (quotes for lowercase):
Environment options are, in effect, considered to be just like any other command-line options, except that they are effectively the first options on the command line. To override an environment option, one may use the ``minus operator' to remove it. For instance, to override one of the quiet-flags in the example above, use the command
The first hyphen is the normal switch character, and the second is a minus sign, acting on the
(the two are equivalent). This may seem awkward or confusing, but it is reasonably intuitive: just ignore the first hyphen and go from there. It is also consistent with the behavior of Unix nice.
As suggested by the examples above, the default variable names are UNZIP_OPTS for VMS (where the symbol used to install unzip as a foreign command would otherwise be confused with the environment variable), and UNZIP for all other operating systems. For compatibility with zip, UNZIPOPT is also accepted (don't ask). If both UNZIP and UNZIPOPT are defined, however, UNZIP takes precedence. unzip's diagnostic option (
The timezone variable (TZ) should be set according to the local timezone in order for the
TK_ARCHIVE_CHARSET will instruct unzip how to interpret file names and commants in an archive. Settings are:
The value must be one of ASCII_ANSI, ASCII_OEM, or UTF-8 (or their equivalents) as described in the File Character Formats section of the unicode reference page.
Setting TK_ARCHIVE_CHARSET to ASCII_ANSI or ASCII_OEM is somewhat like to the LANG environment variable on UNIX in that it tailors the interpretation of the character set in use for file names and comments inside the zip archive.
When this variable is unset or it is set to a value other than those listed earlier, the default ANSI character set is used.
DECRYPTION
Encrypted archives are fully supported by Info-ZIP software, but due to United States export restrictions, de-/encryption support might be disabled in your compiled binary. However, since spring 2000, US export restrictions have been liberated, and our source archives do now include full crypt code. In case you need binary distributions with crypt support enabled, see the file ``WHERE' in any Info-ZIP source or binary distribution for locations both inside and outside the US.
Some compiled versions of unzip may not support decryption (The PTC MKS Toolkit version is compiled with decryption enabled). To check a version for crypt support, either attempt to test or extract an encrypted archive, or else check unzip's diagnostic screen (see the
As noted above, the
If the first password fails the header check on some file, unzip will prompt for another password, and so on until all files are extracted. If a password is not known, entering a null password (that is, just a carriage return or ``Enter') is taken as a signal to skip all further prompting. Only unencrypted files in the archive(s) will thereafter be extracted. (In fact, that's not quite true; older versions of zip and zipcloak allowed null passwords, so unzip checks each encrypted file to see if the null password works. This may result in ``false positives' and extraction errors, as noted above.)
Archives encrypted with 8-bit passwords (for example, passwords with accented European characters) may not be portable across systems and/or other archivers. This problem stems from the use of multiple encoding methods for such characters, including Latin-1 (ISO 8859-1) and OEM code page 850. DOS PKZIP 2.04g uses the OEM code page; Windows PKZIP 2.50 uses Latin-1 (and is therefore incompatible with DOS PKZIP); Info-ZIP uses the OEM code page on DOS, OS/2 and Win3.x ports but ISO coding (Latin-1 etc.) everywhere else; and Nico Mak's WinZip 6.x does not allow 8-bit passwords at all. UnZip 5.3 (or newer) attempts to use the default character set first (e.g., Latin-1), followed by the alternate one (e.g., OEM code page) to test passwords. On EBCDIC systems, if both of these fail, EBCDIC encoding will be tested as a last resort. (EBCDIC is not tested on non-EBCDIC systems, because there are no known archivers that encrypt using EBCDIC encoding.) ISO character encodings other than Latin-1 are not supported. The new addition of (partially) Unicode (resp. UTF-8) support in UnZip 6.0 has not yet been adapted to the encryption password handling in unzip. On systems that use UTF-8 as native character encoding, unzip simply tries decryption with the native UTF-8 encoded password; the built-in attempts to check the password in translated encoding have not yet been adapted for UTF-8 support and will consequently fail.
EXAMPLES
To use unzip to extract all members of the archive letters.zip into the current directory and subdirectories below it, creating any subdirectories as necessary:
To extract all members of letters.zip into the current directory only:
To test letters.zip, printing only a summary message indicating whether the archive is OK or not:
To test all zipfiles in the current directory, printing only the summaries:
(The backslash before the asterisk is only required if the shell expands wildcards, as in Unix; double quotes could have been used instead, as in the source examples below.) To extract to standard output all members of letters.zip whose names end in .tex, auto-converting to the local end-of-line convention and piping the output into more:
To extract the binary file paper1.dvi to standard output and pipe it to a printing program:
To extract all FORTRAN and C source files--*.f, *.c, *.h, and Makefile--into the /tmp directory:
(the double quotes are necessary only in Unix (and PTC MKS Toolkit shells) and only if globbing is turned on). To extract all FORTRAN and C source files, regardless of case (e.g., both *.c and *.C, and any makefile, Makefile, MAKEFILE or similar):
To extract any such files but convert any uppercase MS-DOS or VMS names to lowercase and convert the line-endings of all of the files to the local standard (without respect to any files that might be marked ``binary'):
To extract only newer versions of the files already in the current directory, without querying (NOTE: be careful of unzipping in one timezone a zipfile created in another--ZIP archives other than those created by Zip 2.1 or later contain no timezone information, and a ``newer' file from an eastern timezone may, in fact, be older):
To extract newer versions of the files already in the current directory and to create any files not already there (same caveat as previous example):
To display a diagnostic screen showing which unzip and zipinfo options are stored in environment variables, whether decryption support was compiled in, the compiler with which unzip was compiled, etc.:
In the last five examples, assume that UNZIP or UNZIP_OPTS is set to
To do a doubly quiet listing:
(Note that the ``.zip' is generally not necessary.) To do a standard listing:
or
or
(Extra minuses in options don't hurt.)
TIPS
The current maintainer, being a lazy sort, finds it very useful to define a pair of aliases: tt for ``unzip -tq' and ii for unzip
The maintainer also finds it useful to set the UNZIP environment variable to ``
DIAGNOSTICS
The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:
normal; no errors or warnings detected.
one or more warning errors were encountered, but processing completed successfully anyway. This includes zipfiles where one or more files was skipped due to unsupported compression method or encryption with an unknown password.
a generic error in the zipfile format was detected. Processing may have completed successfully anyway; some broken zipfiles created by other archivers have simple work-arounds.
a severe error in the zipfile format was detected. Processing probably failed immediately.
unzip was unable to allocate memory for one or more buffers during program initialization.
unzip was unable to allocate memory or unable to obtain a tty to read the decryption password(s).
unzip was unable to allocate memory during decompression to disk.
unzip was unable to allocate memory during in-memory decompression.
[currently not used]
the specified zipfiles were not found.
invalid options were specified on the command line.
no matching files were found.
the disk is (or was) full during extraction.
the end of the ZIP archive was encountered prematurely.
the user aborted unzip prematurely with control-C (or similar)
testing or extraction of one or more files failed due to unsupported compression methods or unsupported decryption.
no files were found due to bad decryption password(s). (If even one file is successfully processed, however, the exit status is 1.)
VMS interprets standard Unix (or PC) return values as other, scarier-looking things, so unzip instead maps them into VMS-style status codes. The current mapping is as follows: 1 (success) for normal exit, 0x7fff0001 for warning errors, and (0x7fff000? + 16*normal_unzip_exit_status) for all other errors, where the `?' is 2 (error) for unzip values 2, 9-11 and 80-82, and 4 (fatal error) for the remaining ones (3-8, 50, 51). In addition, there is a compilation option to expand upon this behavior: defining RETURN_CODES results in a human-readable explanation of what the error status means.
BUGS
Multi-part archives are not yet supported, except in conjunction with zip. (All parts must be concatenated together in order, and then ``zip -F' (for zip 2.x) or ``zip -FF' (for zip 3.x) must be performed on the concatenated archive in order to ``fix' it. Also, zip 3.0 and later can combine multi-part (split) archives into a combined single-file archive using ``zip -s- inarchive -O outarchive'. See the zip 3 manual page for more information.) This will definitely be corrected in the next major release. Archives read from standard input are not yet supported, except with funzip (and then only the first member of the archive can be extracted).
Archives encrypted with 8-bit passwords (e.g., passwords with accented European characters) may not be portable across systems and/or other archivers. See the discussion in DECRYPTION above.
unzip's
Dates, times and permissions of stored directories are not restored except under Unix and PTC MKS Toolkit. (On Windows NT and successors, timestamps are now restored.)
[MS-DOS] When extracting or testing files from an archive on a defective floppy diskette, if the ``Fail' option is chosen from DOS's ``Abort, Retry, Fail?' message, older versions of unzip may hang the system, requiring a reboot. This problem appears to be fixed, but control-C (or control-Break) can still be used to terminate unzip.
Under DEC Ultrix, unzip would sometimes fail on long zipfiles (bad CRC, not always reproducible). This was apparently due either to a hardware bug (cache memory) or an operating system bug (improper handling of page faults?). Since Ultrix has been abandoned in favor of Digital Unix (OSF/1), this may not be an issue anymore.
[Unix and PTC MKS Toolkit] Unix special files such as FIFO buffers (named pipes), block devices and character devices are not restored even if they are somehow represented in the zipfile, nor are hard-linked files relinked. Basically the only file types restored by unzip are regular files, directories and symbolic (soft) links.
[OS/2] Extended attributes for existing directories are only updated if the -o (``overwrite all') option is given. This is a limitation of the operating system; because directories only have a creation time associated with them, unzip has no way to determine whether the stored attributes are newer or older than those on disk. In practice this may mean a two-pass approach is required: first unpack the archive normally (with or without freshening/updating existing files), then overwrite just the directory entries (e.g., ``unzip -o foo */').
[VMS] When extracting to another directory, only the [.foo] syntax is accepted for the -d option; the simple Unix foo syntax is silently ignored (as is the less common VMS foo.dir syntax).
[VMS] When the file being extracted already exists, unzip's query only allows skipping, overwriting or renaming; there should additionally be a choice for creating a new version of the file. In fact, the ``overwrite' choice does create a new version; the old version is not overwritten or deleted.
AUTHORS
The primary Info-ZIP authors (current semi-active members of the Zip-Bugs workgroup) are: Ed Gordon (Zip, general maintenance, shared code, Zip64, Win32, Unix, Unicode); Christian Spieler (UnZip maintenance coordination, VMS, MS-DOS, Win32, shared code, general Zip and UnZip integration and optimization); Onno van der Linden (Zip); Mike White (Win32, Windows GUI, Windows DLLs); Kai Uwe Rommel (OS/2, Win32); Steven M. Schweda (VMS, Unix, support of new features); Paul Kienitz (Amiga, Win32, Unicode); Chris Herborth (BeOS, QNX, Atari); Jonathan Hudson (SMS/QDOS); Sergio Monesi (Acorn RISC OS); Harald Denker (Atari, MVS); John Bush (Solaris, Amiga); Hunter Goatley (VMS, Info-ZIP Site maintenance); Steve Salisbury (Win32); Steve Miller (Windows CE GUI), Johnny Lee (MS-DOS, Win32, Zip64); and Dave Smith (Tandem NSK).
The following people were former members of the Info-ZIP development group and provided major contributions to key parts of the current code: Greg ``Cave Newt' Roelofs (UnZip, unshrink decompression); Jean-loup Gailly (deflate compression); Mark Adler (inflate decompression, fUnZip).
The author of the original unzip code upon which Info-ZIP's was based is Samuel H. Smith; Carl Mascott did the first Unix port; and David P. Kirschbaum organized and led Info-ZIP in its early days with Keith Petersen hosting the original mailing list at WSMR-SimTel20. The full list of contributors to UnZip has grown quite large; please refer to the CONTRIBS file in the UnZip source distribution for a relatively complete version.
VERSIONS
Samuel H. Smith
Samuel H. Smith
many Usenet contributors
Info-ZIP (DPK, consolidator)
Info-ZIP (DPK, consolidator)
Info-ZIP (GRR, maintainer)
Info-ZIP
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, GRR)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
Info-ZIP (Zip-Bugs subgroup, SPC)
PORTABILITY
All UNIX systems. Windows 7. Windows Server 2008 R2. Windows 8. Windows Server 2012. Windows 10. Windows Server 2016. Windows Server 2019.
unzip is also available other systems including MSDOS, OS/2, Minix, Atari, Macintosh, Amiga, and Acorn RISC OS.
AVAILABILITY
PTC MKS Toolkit for Power Users
PTC MKS Toolkit for System Administrators
PTC MKS Toolkit for Developers
PTC MKS Toolkit for Interoperability
PTC MKS Toolkit for Professional Developers
PTC MKS Toolkit for Professional Developers 64-Bit Edition
PTC MKS Toolkit for Enterprise Developers
PTC MKS Toolkit for Enterprise Developers 64-Bit Edition
SEE ALSO
- Commands:
- bzdiff, bzgrep, bzip2, bzmore, cpio, funxip, gzip, mkszip, pax, tar, uncompress, unpack, zcat, zip, zipcloak, zipgrep, zipinfo, zipnote, zipsplit
PTC MKS Toolkit Backup and Tape Handling Solutions Guide
PTC MKS Toolkit 10.2 Documentation Build 28.