how to uninstall php 8 in ubuntu 18.04 completely

September 6, 2022 in Tips and Tricks, Ubuntu

linux zip exclude file extension

 sudo zip public_html.zip public_html/ -r -x \*.mp4 -x \*.mp3 -x \*.mov -x \*.zip

 sudo zip -r public_html.zip public_html/  -x \*.mp4 -x \*.mp3 -x \*.mov -x \*.zip -x \*.mkv

July 4, 2022 in Tips and Tricks, Ubuntu

UNZIP COMMAND IN UNIX / LINUX

UNZIP(1L)                                                                                                                                                 UNZIP(1L)



NAME
       unzip - list, test and extract compressed files in a ZIP archive

SYNOPSIS
       unzip [-Z] [-cflptTuvz[abjnoqsCDKLMUVWX$/:^]] file[.zip] [file(s) ...]  [-x xfile(s) ...] [-d exdir]

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(1L), 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.

ARGUMENTS
       file[.zip]
              Path  of the ZIP archive(s).  If the file specification is a wildcard, each matching file is processed in an order determined by the operating system
              (or file system).  Only the filename can be a wildcard; the path itself cannot.  Wildcard expressions are similar to those supported in commonly used
              Unix shells (sh, ksh, csh) and may contain:

              *      matches a sequence of 0 or more characters

              ?      matches exactly 1 character

              [...]  matches  any single character found inside the brackets; ranges are specified by a beginning character, a hyphen, and an ending character.  If
                     an exclamation point or a caret (`!' or `^') follows the left bracket, then the range of characters within the brackets is complemented  (that
                     is,  anything  except  the  characters  inside  the  brackets is considered a match).  To specify a verbatim left bracket, the three-character
                     sequence ``[[]'' has to be used.

              (Be sure to quote any character that might otherwise be interpreted or modified by the operating system, particularly under Unix  and  VMS.)   If  no
              matches  are  found,  the  specification  is  assumed to be a literal filename; and if that also fails, the suffix .zip is appended.  Note that self-
              extracting ZIP files are supported, as with any other ZIP archive; just specify the .exe suffix (if any) explicitly.

       [file(s)]
              An optional list of archive members to be processed, separated by spaces.  (VMS versions compiled with VMSCLI defined must delimit files with  commas
              instead.   See  -v  in  OPTIONS  below.)   Regular expressions (wildcards) may be used to match multiple members; see above.  Again, be sure to quote
              expressions that would otherwise be expanded or modified by the operating system.

       [-x xfile(s)]
              An optional list of archive members to be excluded from processing.  Since wildcard characters normally match (`/') directory separators (for  excep‐
              tions  see  the  option -W), this option may be used to exclude any files that are in subdirectories.  For example, ``unzip foo *.[ch] -x */*'' would
              extract all C source files in the main directory, but none in any subdirectories.  Without the -x option, all  C  source  files  in  all  directories
              within the zipfile would be extracted.

       [-d exdir]
              An  optional  directory  to  which  to extract files.  By default, all files and subdirectories are recreated in the current directory; the -d option
              allows extraction in an arbitrary directory (always assuming one has permission to write to the directory).  This option need not appear at  the  end
              of  the command line; it is also accepted before the zipfile specification (with the normal options), immediately after the zipfile specification, or
              between the file(s) and the -x option.  The option and directory may be concatenated without any white space between them, but  note  that  this  may
              cause  normal  shell behavior to be suppressed.  In particular, ``-d ~'' (tilde) is expanded by Unix C shells into the name of the user's home direc‐
              tory, but ``-d~'' is treated as a literal subdirectory ``~'' of the current directory.

OPTIONS
       Note that, in order to support obsolescent hardware, unzip's usage screen is limited to 22 or 23 lines and should therefore be considered only a reminder of
       the basic unzip syntax rather than an exhaustive list of all possible flags.  The exhaustive list follows:

       -Z     zipinfo(1L)  mode.   If  the  first option on the command line is -Z, the remaining options are taken to be zipinfo(1L) options.  See the appropriate
              manual page for a description of these options.

       -A     [OS/2, Unix DLL] print extended help for the DLL's programming interface (API).

       -c     extract files to stdout/screen (``CRT'').  This option is similar to the -p option except that the name of each file is printed as it  is  extracted,
              the  -a  option  is  allowed,  and  ASCII-EBCDIC  conversion is automatically performed if appropriate.  This option is not listed in the unzip usage
              screen.

       -f     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  -o option may be used to suppress the queries.  Note that under many operating systems, the TZ (timezone) environment
              variable must be set correctly in order for -f and -u to work properly (under Unix the variable is usually set automatically).  The reasons for  this
              are  somewhat  subtle but have to do with the differences between DOS-format file times (always local time) and Unix-format times (always in GMT/UTC)
              and the necessity to compare the two.  A typical TZ value is ``PST8PDT'' (US Pacific time with automatic adjustment  for  Daylight  Savings  Time  or
              ``summer time'').

       -l     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 -l option also lists columns  for  the  sizes  of  stored  OS/2
              extended  attributes  (EAs)  and  OS/2  access control lists (ACLs).  In addition, the zipfile comment and individual file comments (if any) are dis‐
              played.  If a file was archived from a single-case file system (for example, the old MS-DOS FAT file system) and the -L option was given,  the  file‐
              name is converted to lowercase and is prefixed with a caret (^).

       -p     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).

       -t     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.

       -T     [most  OSes]  set the timestamp on the archive(s) to that of the newest file in each one.  This corresponds to zip's -go option except that it can be
              used on wildcard zipfiles (e.g., ``unzip -T \*.zip'') and is much faster.

       -u     update existing files and create new ones if needed.  This option performs the same function as the -f option, extracting (with query) files that are
              newer than those with the same name on disk, and in addition it extracts those files that do not already exist on disk.  See -f above for information
              on setting the timezone properly.

       -v     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, -v lists archive files verbosely, adding to the basic -l info the
              compression method, compressed size, compression ratio and 32-bit CRC.  In contrast to most of the competing utilities, unzip removes  the  12  addi‐
              tional  header bytes of encrypted entries from the compressed size numbers.  Therefore, compressed size and compression ratio figures are independent
              of the entry's encryption status and show the correct compression performance.  (The complete size of the encrypted compressed data stream  for  zip‐
              file entries is reported by the more verbose zipinfo(1L) reports, see the separate manual.)  When no zipfile is specified (that is, the complete com‐
              mand is simply ``unzip -v''), a diagnostic screen is printed.  In addition to the normal header with release date and version, unzip lists  the  home
              Info-ZIP  ftp site and where to find a list of other ftp and non-ftp sites; the target operating system for which it was compiled, as well as (possi‐
              bly) the hardware on which it was compiled, the compiler and version used, and the compilation date;  any  special  compilation  options  that  might
              affect  the  program's operation (see also DECRYPTION below); and any options stored in environment variables that might do the same (see ENVIRONMENT
              OPTIONS below).  As a modifier it works in conjunction with other options (e.g., -t) to produce more verbose or debugging output;  this  is  not  yet
              fully implemented but will be in future releases.

       -z     display only the archive comment.

MODIFIERS
       -a     convert  text  files.  Ordinarily all files are extracted exactly as they are stored (as ``binary'' files).  The -a option causes files identified by
              zip as text files (those with the `t' label in zipinfo listings, rather than `b') to be automatically extracted as  such,  converting  line  endings,
              end-of-file  characters  and  the character set itself as necessary.  (For example, Unix files use line feeds (LFs) for end-of-line (EOL) and have no
              end-of-file (EOF) marker; Macintoshes use carriage returns (CRs) for EOLs; and most PC operating systems use CR+LF for EOLs and  control-Z  for  EOF.
              In  addition,  IBM  mainframes and the Michigan Terminal System use EBCDIC rather than the more common ASCII character set, and NT supports Unicode.)
              Note that zip's identification of text files is by no means perfect; some ``text'' files may actually be binary  and  vice  versa.   unzip  therefore
              prints  ``[text]''  or  ``[binary]''  as  a  visual  check for each file it extracts when using the -a option.  The -aa option forces all files to be
              extracted as text, regardless of the supposed file type.  On VMS, see also -S.

       -b     [general] treat all files as binary (no text conversions).  This is a shortcut for ---a.

       -b     [Tandem] force the creation files with filecode type 180 ('C') when extracting Zip entries marked as "text". (On Tandem, -a is  enabled  by  default,
              see above).

       -b     [VMS]  auto-convert  binary files (see -a above) to fixed-length, 512-byte record format.  Doubling the option (-bb) forces all files to be extracted
              in this format. When extracting to standard output (-c or -p option in effect), the default conversion of text  record  delimiters  is  disabled  for
              binary (-b) resp. all (-bb) files.

       -B     [when compiled with UNIXBACKUP defined] 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 -o, numbered backup files are never created. In this case, all backup files
              are named as the original file with an appended tilde, existing backup files are deleted without notice.  This feature works similarly to the default
              behavior of emacs(1) in many locations.

              Example: the old copy of ``foo'' is renamed to ``foo~''.

              Warning:  Users should be aware that the -B option does not prevent loss of existing data under all circumstances.  For example, when unzip is run in
              overwrite-all mode, an existing ``foo~'' file is deleted before unzip attempts to rename  ``foo''  to  ``foo~''.   When  this  rename  attempt  fails
              (because  of  a  file locks, insufficient privileges, or ...), the extraction of ``foo~'' gets cancelled, but the old backup file is already lost.  A
              similar scenario takes place when the sequence number range for numbered backup files gets exhausted (99999, or 65535 for 16-bit systems).   In  this
              case, the backup file with the maximum sequence number is deleted and replaced by the new backup version without notice.

       -C     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 -L/-U change; see the relevant options below).  Because some file  systems  are  fully
              case-sensitive  (notably those under the Unix operating system) and because both ZIP archives and unzip itself are portable across platforms, unzip's
              default behavior is to match both wildcard and literal filenames case-sensitively.  That is, specifying ``makefile'' on the command  line  will  only
              match  ``makefile''  in the archive, not ``Makefile'' or ``MAKEFILE'' (and similarly for wildcard specifications).  Since this does not correspond to
              the behavior of many other operating/file systems (for example, OS/2 HPFS, which preserves mixed case but is not sensitive to it), the -C option  may
              be  used to force all filename matches to be case-insensitive.  In the example above, all three files would then match ``makefile'' (or ``make*'', or
              similar).  The -C option affects file specs in both the normal file list and the excluded-file list (xlist).

              Please note that the -C option does neither affect the search for the zipfile(s) nor the matching of archive entries to existing files on the extrac‐
              tion path.  On a case-sensitive file system, unzip will never try to overwrite a file ``FOO'' when extracting an entry ``foo''!

       -D     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 -D, unzip is told to suppress restoration of timestamps for
              directories  explicitly  created  from  Zip archive entries.  This option only applies to ports that support setting timestamps for directories (cur‐
              rently ATheOS, BeOS, MacOS, OS/2, Unix, VMS, Win32, for other unzip ports, -D has no effect).  The duplicated option -DD forces suppression of  time‐
              stamp  restoration for all extracted entries (files and directories).  This option results in setting the timestamps for all extracted entries to the
              current time.

              On VMS, the default setting for this option is -D for consistency with the behaviour of BACKUP: file timestamps are restored, timestamps of extracted
              directories  are  left  at the current time.  To enable restoration of directory timestamps, the negated option --D should be specified.  On VMS, the
              option -D disables timestamp restoration for all extracted Zip archive items.  (Here, a single -D on the command line combines with the default -D to
              do what an explicit -DD does on other systems.)

       -E     [MacOS only] display contents of MacOS extra field during restore operation.

       -F     [Acorn only] suppress removal of NFS filetype extension from stored filenames.

       -F     [non-Acorn  systems supporting long filenames with embedded commas, and only if compiled with ACORN_FTYPE_NFS defined] 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.)

       -i     [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.

       -j     junk paths.  The archive's directory structure is not recreated; all files are deposited in the extraction directory (by default, the current one).

       -J     [BeOS only] junk file attributes.  The file's BeOS file attributes are not restored, just the file's data.

       -J     [MacOS only] ignore MacOS extra fields.  All Macintosh specific info is skipped. Data-fork and resource-fork are restored as separate files.

       -K     [AtheOS, BeOS, Unix only] retain SUID/SGID/Tacky file attributes.  Without this flag, these attribute bits are cleared for security reasons.

       -L     convert to lowercase any filename originating on an uppercase-only operating system or file system.  (This was unzip's default behavior  in  releases
              prior  to  5.11;  the new default behavior is identical to the old behavior with the -U option, which is now obsolete and will be removed in a future
              release.)  Depending on the archiver, files archived under single-case file systems (VMS, old MS-DOS FAT, etc.) may be stored as all-uppercase names;
              this  can  be ugly or inconvenient when extracting to a case-preserving file system such as OS/2 HPFS or a case-sensitive one such as under Unix.  By
              default unzip lists and extracts such filenames exactly as they're stored (excepting truncation, conversion of unsupported  characters,  etc.);  this
              option causes the names of all files from certain systems to be converted to lowercase.  The -LL option forces conversion of every filename to lower‐
              case, regardless of the originating file system.

       -M     pipe all output through an internal pager similar to the Unix more(1) command.  At the end of a screenful of output, unzip pauses with a ``--More--''
              prompt; the next screenful may be viewed by pressing the Enter (Return) key or the space bar.  unzip can be terminated by pressing the ``q'' key and,
              on some systems, the Enter/Return key.  Unlike Unix more(1), there is no forward-searching or editing capability.  Also, unzip doesn't notice if long
              lines  wrap  at  the edge of the screen, effectively resulting in the printing of two or more lines and the likelihood that some text will scroll off
              the top of the screen before being viewed.  On some systems the number of available lines on the screen is not detected, in which case unzip  assumes
              the height is 24 lines.

       -n     never  overwrite  existing  files.   If  a  file already exists, skip the extraction of that file without prompting.  By default unzip queries before
              extracting any file that already exists; the user may choose to overwrite only the current file, overwrite all files, skip extraction of the  current
              file, skip extraction of all existing files, or rename the current file.

       -N     [Amiga]  extract  file comments as Amiga filenotes.  File comments are created with the -c option of zip(1L), or with the -N option of the Amiga port
              of zip(1L), which stores filenotes as comments.

       -o     overwrite existing files without prompting.  This is a dangerous option, so use it with care.  (It is often used with -f, however, and  is  the  only
              way to overwrite directory EAs under OS/2.)

       -P password
              use  password  to  decrypt encrypted zipfile entries (if any).  THIS IS INSECURE!  Many multi-user operating systems provide ways for any user to see
              the current command line of any other user; even on stand-alone systems there is always the threat of over-the-shoulder peeking.  Storing the  plain‐
              text  password  as  part of a command line in an automated script is even worse.  Whenever possible, use the non-echoing, interactive prompt to enter
              passwords.  (And where security is truly important, use strong encryption such as Pretty Good Privacy instead of the relatively weak encryption  pro‐
              vided by standard zipfile utilities.)

       -q     perform  operations quietly (-qq = even quieter).  Ordinarily unzip prints the names of the files it's extracting or testing, the extraction methods,
              any file or zipfile comments that may be stored in the archive, and possibly a summary when finished with each archive.  The -q[q]  options  suppress
              the printing of some or all of these messages.

       -s     [OS/2,  NT,  MS-DOS] convert spaces in filenames to underscores.  Since all PC operating systems allow spaces in filenames, unzip by default extracts
              filenames with spaces intact (e.g., ``EA DATA. SF'').  This can be awkward, however, since MS-DOS in particular does not gracefully support spaces in
              filenames.  Conversion of spaces to underscores can eliminate the awkwardness in some cases.

       -S     [VMS]  convert text files (-a, -aa) into Stream_LF record format, instead of the text-file default, variable-length record format.  (Stream_LF is the
              default record format of VMS unzip. It is applied unless conversion (-a, -aa and/or -b, -bb) is requested or a VMS-specific entry is processed.)

       -U     [UNICODE_SUPPORT only] modify or disable UTF-8 handling.  When UNICODE_SUPPORT is available, the option -U forces unzip to escape all non-ASCII char‐
              acters  from  UTF-8  coded  filenames  as ``#Uxxxx'' (for UCS-2 characters, or ``#Lxxxxxx'' for unicode codepoints needing 3 octets).  This option is
              mainly provided for debugging purpose when the fairly new UTF-8 support is suspected to mangle up extracted filenames.

              The option -UU allows to entirely disable the recognition of UTF-8 encoded filenames.  The handling of filename codings within unzip  falls  back  to
              the behaviour of previous versions.

              [old, obsolete usage] leave filenames uppercase if created under MS-DOS, VMS, etc.  See -L above.

       -V     retain (VMS) file version numbers.  VMS files can be stored with a version number, in the format file.ext;##.  By default the ``;##'' version numbers
              are stripped, but this option allows them to be retained.  (On file systems that limit filenames to particularly short lengths, the  version  numbers
              may be truncated or stripped regardless of this option.)

       -W     [only  when  WILD_STOP_AT_DIR  compile-time  option  enabled]  modifies  the pattern matching routine so that both `?' (single-char wildcard) and `*'
              (multi-char wildcard) do not match the directory separator character `/'.  (The two-character sequence ``**'' acts  as  a  multi-char  wildcard  that
              includes the directory separator in its matched characters.)  Examples:

           "*.c" matches "foo.c" but not "mydir/foo.c"
           "**.c" matches both "foo.c" and "mydir/foo.c"
           "*/*.c" matches "bar/foo.c" but not "baz/bar/foo.c"
           "??*/*" matches "ab/foo" and "abc/foo"
                   but not "a/foo" or "a/b/foo"

              This  modified behaviour is equivalent to the pattern matching style used by the shells of some of UnZip's supported target OSs (one example is Acorn
              RISC OS).  This option may not be available on systems where the Zip archive's internal directory separator character `/' is allowed as regular char‐
              acter  in native operating system filenames.  (Currently, UnZip uses the same pattern matching rules for both wildcard zipfile specifications and zip
              entry selection patterns in most ports.  For systems allowing `/' as regular filename character, the -W option would not work as expected on a  wild‐
              card zipfile specification.)

       -X     [VMS,  Unix, OS/2, NT, Tandem] restore owner/protection info (UICs and ACL entries) under VMS, or user and group info (UID/GID) under Unix, or access
              control lists (ACLs) under certain network-enabled versions of OS/2 (Warp Server with IBM LAN Server/Requester 3.0 to 5.0; Warp Connect with IBM Peer
              1.0), or security ACLs under Windows NT.  In most cases this will require special system privileges, and doubling the option (-XX) under NT instructs
              unzip to use privileges for extraction; but under Unix, for example, a user who belongs to several groups can restore files owned  by  any  of  those
              groups,  as long as the user IDs match his or her own.  Note that ordinary file attributes are always restored--this option applies only to optional,
              extra ownership info available on some operating systems.  [NT's access control lists do not appear to be especially compatible with  OS/2's,  so  no
              attempt is made at cross-platform portability of access privileges.  It is not clear under what conditions this would ever be useful anyway.]

       -Y     [VMS] treat archived file name endings of ``.nnn'' (where ``nnn'' is a decimal  number) as if they were VMS version numbers (``;nnn'').  (The default
              is to treat them as file types.)  Example:
                   "a.b.3" -> "a.b;3".

       -$     [MS-DOS, OS/2, NT] restore the volume label if the extraction medium is removable (e.g., a diskette).  Doubling the option (-$$) allows  fixed  media
              (hard disks) to be labeled as well.  By default, volume labels are ignored.

       -/ extensions
              [Acorn  only]  overrides  the extension list supplied by Unzip$Ext environment variable. During extraction, filename extensions that match one of the
              items in this extension list are swapped in front of the base name of the extracted file.

       -:     [all but Acorn, VM/CMS, MVS, Tandem] allows to extract archive members into locations outside of the current `` extraction root folder''.  For  secu‐
              rity reasons, unzip normally removes ``parent dir'' path components (``../'') from the names of extracted file.  This safety feature (new for version
              5.50) prevents unzip from accidentally writing files to ``sensitive'' areas outside the active extraction folder tree head.  The -: option lets unzip
              switch  back  to  its previous, more liberal behaviour, to allow exact extraction of (older) archives that used ``../'' components to create multiple
              directory trees at the level of the current extraction folder.  This option does not enable writing explicitly to the  root  directory  (``/'').   To
              achieve this, it is necessary to set the extraction target folder to root (e.g. -d / ).  However, when the -: option is specified, it is still possi‐
              ble to implicitly write to the root directory by specifying enough ``../'' path components within the zip archive.  Use this option with extreme cau‐
              tion.

       -^     [Unix only] allow control characters in names of extracted ZIP archive entries.  On Unix, a file name may contain any (8-bit) character code with the
              two exception '/' (directory delimiter) and NUL (0x00, the C string termination indicator), unless the specific file system has more restrictive con‐
              ventions.   Generally,  this  allows  to embed ASCII control characters (or even sophisticated control sequences) in file names, at least on 'native'
              Unix file systems.  However, it may be highly suspicious to make use of this Unix "feature".  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 han‐
              dle 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 -^ option allows to override this filter in the rare case that
              embedded filename control characters are to be intentionally restored.

       -2     [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 desti‐
              nation file system.

ENVIRONMENT OPTIONS
       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 -a, -L, -C, -q, -o, or -n modifiers:  make unzip auto-convert text files by default, make it convert filenames from uppercase systems to lowercase,
       make it match names case-insensitively, make it quieter, or make it always overwrite or never overwrite files as it extracts them.   For  example,  to  make
       unzip act as quietly as possible, only reporting errors, one would use one of the following commands:

         Unix Bourne shell:
              UNZIP=-qq; export UNZIP

         Unix C shell:
              setenv UNZIP -qq

         OS/2 or MS-DOS:
              set UNZIP=-qq

         VMS (quotes for lowercase):
              define UNZIP_OPTS "-qq"

       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

       unzip --q[other options] zipfile

       The  first  hyphen is the normal switch character, and the second is a minus sign, acting on the q option.  Thus the effect here is to cancel one quantum of
       quietness.  To cancel both quiet flags, two (or more) minuses may be used:

       unzip -t--q zipfile
       unzip ---qt zipfile

       (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(1).

       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(1L), UNZIPOPT is also  accepted
       (don't  ask).   If both UNZIP and UNZIPOPT are defined, however, UNZIP takes precedence.  unzip's diagnostic option (-v with no zipfile name) can be used to
       check the values of all four possible unzip and zipinfo environment variables.

       The timezone variable (TZ) should be set according to the local timezone in order for the -f and -u to operate correctly.  See the description of  -f  above
       for  details.   This  variable  may  also be necessary to get timestamps of extracted files to be set correctly.  The WIN32 (Win9x/ME/NT4/2K/XP/2K3) port of
       unzip gets the timezone configuration from the registry, assuming it is correctly set in the Control Panel.  The TZ variable is ignored for this port.

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.  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 -v option above) for ``[decryption]'' as one of the special compilation options.

       As noted above, the -P option may be used to supply a password on the command line, but at a cost in security.  The preferred decryption method is simply to
       extract normally; if a zipfile member is encrypted, unzip will prompt for the password without echoing what is typed.  unzip continues to use the same pass‐
       word as long as it appears to be valid, by testing a 12-byte header on each file.  The correct password will always check out against the header, but  there
       is  a  1-in-256  chance  that  an  incorrect  password will as well.  (This is a security feature of the PKWARE zipfile format; it helps prevent brute-force
       attacks that might otherwise gain a large speed advantage by testing only the header.)  In the case that an incorrect password is given but  it  passes  the
       header test anyway, either an incorrect CRC will be generated for the extracted data or else unzip will fail during the extraction because the ``decrypted''
       bytes do not constitute a valid compressed data stream.

       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(1L) and zipcloak(1L) 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 neces‐
       sary:

       unzip letters

       To extract all members of letters.zip into the current directory only:

       unzip -j letters

       To test letters.zip, printing only a summary message indicating whether the archive is OK or not:

       unzip -tq letters

       To test all zipfiles in the current directory, printing only the summaries:

       unzip -tq \*.zip

       (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(1):

       unzip -ca letters \*.tex | more

       To extract the binary file paper1.dvi to standard output and pipe it to a printing program:

       unzip -p articles paper1.dvi | dvips

       To extract all FORTRAN and C source files--*.f, *.c, *.h, and Makefile--into the /tmp directory:

       unzip source.zip "*.[fch]" Makefile -d /tmp

       (the double quotes are necessary only in Unix 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):

       unzip -C source.zip "*.[fch]" makefile -d /tmp

       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''):

       unzip -aaCL source.zip "*.[fch]" makefile -d /tmp

       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):

       unzip -fo sources

       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):

       unzip -uo sources

       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.:

       unzip -v

       In the last five examples, assume that UNZIP or UNZIP_OPTS is set to -q.  To do a singly quiet listing:

       unzip -l file.zip

       To do a doubly quiet listing:

       unzip -ql file.zip

       (Note that the ``.zip'' is generally not necessary.)  To do a standard listing:

       unzip --ql file.zip
       or
       unzip -l-q file.zip
       or
       unzip -l--q file.zip
       (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 -Z'' (or ``zipinfo'').
       One  may  then  simply  type  ``tt  zipfile''  to test an archive, something that is worth making a habit of doing.  With luck unzip will report ``No errors
       detected in compressed data of zipfile.zip,'' after which one may breathe a sigh of relief.

       The maintainer also finds it useful to set the UNZIP environment variable to ``-aL'' and is tempted to add ``-C'' as well.  His ZIPINFO variable is  set  to
       ``-z''.

DIAGNOSTICS
       The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:

              0      normal; no errors or warnings detected.

              1      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.

              2      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.

              3      a severe error in the zipfile format was detected.  Processing probably failed immediately.

              4      unzip was unable to allocate memory for one or more buffers during program initialization.

              5      unzip was unable to allocate memory or unable to obtain a tty to read the decryption password(s).

              6      unzip was unable to allocate memory during decompression to disk.

              7      unzip was unable to allocate memory during in-memory decompression.

              8      [currently not used]

              9      the specified zipfiles were not found.

              10     invalid options were specified on the command line.

              11     no matching files were found.

              50     the disk is (or was) full during extraction.

              51     the end of the ZIP archive was encountered prematurely.

              80     the user aborted unzip prematurely with control-C (or similar)

              81     testing or extraction of one or more files failed due to unsupported compression methods or unsupported decryption.

              82     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 compila‐
       tion 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 -M (``more'') option tries to take into account automatic wrapping of long lines. However, the code may fail to detect the  correct  wrapping  loca‐
       tions. First, TAB characters (and similar control sequences) are not taken into account, they are handled as ordinary printable characters.  Second, depend‐
       ing on the actual system / OS port, unzip may not detect the true screen geometry but rather rely on "commonly used" default dimensions.  The  correct  han‐
       dling of tabs would require the implementation of a query for the actual tabulator setup on the output console.

       Dates, times and permissions of stored directories are not restored except under Unix. (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]  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.

SEE ALSO
       funzip(1L), zip(1L), zipcloak(1L), zipgrep(1L), zipinfo(1L), zipnote(1L), zipsplit(1L)

URL
       The Info-ZIP home page is currently at
       http://www.info-zip.org/pub/infozip/
       or
       ftp://ftp.info-zip.org/pub/infozip/ .

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 fea‐
       tures); 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.

July 4, 2022 in Tips and Tricks, Ubuntu

ZIP COMMAND IN UNIX / LINUX

ZIP(1L)                                                                                                                                                     ZIP(1L)



NAME
       zip - package and compress (archive) files

SYNOPSIS
       zip [-aABcdDeEfFghjklLmoqrRSTuvVwXyz!@$] [--longoption ...]  [-b path] [-n suffixes] [-t date] [-tt date] [zipfile [file ...]]  [-xi list]

       zipcloak (see separate man page)

       zipnote (see separate man page)

       zipsplit (see separate man page)

       Note:   Command  line  processing  in zip has been changed to support long options and handle all options and arguments more consistently.  Some old command
       lines that depend on command line inconsistencies may no longer work.

DESCRIPTION
       zip is a compression and file packaging utility for Unix, VMS, MSDOS, OS/2, Windows 9x/NT/XP, Minix, Atari, Macintosh, Amiga, and  Acorn  RISC  OS.   It  is
       analogous to a combination of the Unix commands tar(1) and compress(1) and is compatible with PKZIP (Phil Katz's ZIP for MSDOS systems).

       A  companion  program (unzip(1L)) unpacks zip archives.  The zip and unzip(1L) programs can work with archives produced by PKZIP (supporting most PKZIP fea‐
       tures up to PKZIP version 4.6), and PKZIP and PKUNZIP can work with archives produced by zip (with some exceptions, notably streamed  archives,  but  recent
       changes in the zip file standard may facilitate better compatibility).  zip version 3.0 is compatible with PKZIP 2.04 and also supports the Zip64 extensions
       of PKZIP 4.5 which allow archives as well as files to exceed the previous 2 GB limit (4 GB in some cases).  zip also now supports bzip2 compression  if  the
       bzip2  library  is included when zip is compiled.  Note that PKUNZIP 1.10 cannot extract files produced by PKZIP 2.04 or zip 3.0. You must use PKUNZIP 2.04g
       or unzip 5.0p1 (or later versions) to extract them.

       See the EXAMPLES section at the bottom of this page for examples of some typical uses of zip.

       Large Archives and Zip64.  zip automatically uses the Zip64 extensions when files larger than 4 GB are added to an  archive,  an  archive  containing  Zip64
       entries is updated (if the resulting archive still needs Zip64), the size of the archive will exceed 4 GB, or when the number of entries in the archive will
       exceed about 64K.  Zip64 is also used for archives streamed from standard input as the size of such archives are not known in advance, but the  option  -fz-
       can  be  used  to  force zip to create PKZIP 2 compatible archives (as long as Zip64 extensions are not needed).  You must use a PKZIP 4.5 compatible unzip,
       such as unzip 6.0 or later, to extract files using the Zip64 extensions.

       In addition, streamed archives, entries encrypted with standard encryption, or split archives created with the pause option may not be compatible with PKZIP
       as  data  descriptors are used and PKZIP at the time of this writing does not support data descriptors (but recent changes in the PKWare published zip stan‐
       dard now include some support for the data descriptor format zip uses).


       Mac OS X.  Though previous Mac versions had their own zip port, zip supports Mac OS X as part of the Unix port and most Unix features apply.  References  to
       "MacOS"  below  generally  refer  to MacOS versions older than OS X.  Support for some Mac OS features in the Unix Mac OS X port, such as resource forks, is
       expected in the next zip release.


       For a brief help on zip and unzip, run each without specifying any parameters on the command line.


USE
       The program is useful for packaging a set of files for distribution; for archiving files; and for saving disk space by temporarily compressing unused  files
       or directories.

       The  zip program puts one or more compressed files into a single zip archive, along with information about the files (name, path, date, time of last modifi‐
       cation, protection, and check information to verify file integrity).  An entire directory structure can be packed into a zip archive with a single  command.
       Compression  ratios  of 2:1 to 3:1 are common for text files.  zip has one compression method (deflation) and can also store files without compression.  (If
       bzip2 support is added, zip can also compress using bzip2 compression, but such entries require a reasonably modern unzip to decompress.   When  bzip2  com‐
       pression  is  selected,  it  replaces deflation as the default method.)  zip automatically chooses the better of the two (deflation or store or, if bzip2 is
       selected, bzip2 or store) for each file to be compressed.

       Command format.  The basic command format is

              zip options archive inpath inpath ...

       where archive is a new or existing zip archive and inpath is a directory or file path optionally including wildcards.  When given the name  of  an  existing
       zip  archive,  zip  will  replace identically named entries in the zip archive (matching the relative names as stored in the archive) or add entries for new
       names.  For example, if foo.zip exists and contains foo/file1 and foo/file2, and the directory foo contains the files foo/file1 and foo/file3, then:

              zip -r foo.zip foo

       or more concisely

              zip -r foo foo

       will replace foo/file1 in foo.zip and add foo/file3 to foo.zip.  After this, foo.zip contains foo/file1, foo/file2, and foo/file3, with foo/file2  unchanged
       from before.

       So if before the zip command is executed foo.zip has:

               foo/file1 foo/file2

       and directory foo has:

               file1 file3

       then foo.zip will have:

               foo/file1 foo/file2 foo/file3

       where foo/file1 is replaced and foo/file3 is new.

       -@ file lists.   If  a  file list is specified as -@ [Not on MacOS], zip takes the list of input files from standard input instead of from the command line.
       For example,

              zip -@ foo

       will store the files listed one per line on stdin in foo.zip.

       Under Unix, this option can be used to powerful effect in conjunction with the find (1) command.  For example, to archive all the C source files in the cur‐
       rent directory and its subdirectories:

              find . -name "*.[ch]" -print | zip source -@

       (note that the pattern must be quoted to keep the shell from expanding it).

       Streaming input and output.   zip  will  also  accept a single dash ("-") as the zip file name, in which case it will write the zip file to standard output,
       allowing the output to be piped to another program. For example:

              zip -r - . | dd of=/dev/nrst0 obs=16k

       would write the zip output directly to a tape with the specified block size for the purpose of backing up the current directory.

       zip also accepts a single dash ("-") as the name of a file to be compressed, in which case it will read the file from standard input, allowing zip  to  take
       input from another program. For example:

              tar cf - . | zip backup -

       would compress the output of the tar command for the purpose of backing up the current directory. This generally produces better compression than the previ‐
       ous example using the -r option because zip can take advantage of redundancy between files. The backup can be restored using the command

              unzip -p backup | tar xf -

       When no zip file name is given and stdout is not a terminal, zip acts as a filter, compressing standard input to standard output.  For example,

              tar cf - . | zip | dd of=/dev/nrst0 obs=16k

       is equivalent to

              tar cf - . | zip - - | dd of=/dev/nrst0 obs=16k

       zip archives created in this manner can be extracted with the program funzip which is provided in the unzip package, or by gunzip which is provided  in  the
       gzip package (but some gunzip may not support this if zip used the Zip64 extensions). For example:

              dd if=/dev/nrst0  ibs=16k | funzip | tar xvf -

       The stream can also be saved to a file and unzip used.

       If Zip64 support for large files and archives is enabled and zip is used as a filter, zip creates a Zip64 archive that requires a PKZIP 4.5 or later compat‐
       ible unzip to read it.  This is to avoid amgibuities in the zip file structure as defined in the current zip standard (PKWARE AppNote) where the decision to
       use  Zip64 needs to be made before data is written for the entry, but for a stream the size of the data is not known at that point.  If the data is known to
       be smaller than 4 GB, the option -fz- can be used to prevent use of Zip64, but zip will exit with an error if Zip64 was in fact needed.  zip 3  and  unzip 6
       and  later  can read archives with Zip64 entries.  Also, zip removes the Zip64 extensions if not needed when archive entries are copied (see the -U (--copy)
       option).

       When directing the output to another file, note that all options should be before the redirection including -x.  For example:

              zip archive "*.h" "*.c" -x donotinclude.h orthis.h > tofile

       Zip files.  When changing an existing zip archive, zip will write a temporary file with the new contents, and only replace the old one when the  process  of
       creating the new version has been completed without error.

       If  the  name  of the zip archive does not contain an extension, the extension .zip is added. If the name already contains an extension other than .zip, the
       existing extension is kept unchanged.  However, split archives (archives split over multiple files) require the .zip extension on the last split.

       Scanning and reading files.  When zip starts, it scans for files to process (if needed).  If this scan takes longer than about 5 seconds, zip will display a
       "Scanning  files"  message  and start displaying progress dots every 2 seconds or every so many entries processed, whichever takes longer.  If there is more
       than 2 seconds between dots it could indicate that finding each file is taking time and could mean a slow network connection  for  example.   (Actually  the
       initial  file  scan  is  a  two-step  process where the directory scan is followed by a sort and these two steps are separated with a space in the dots.  If
       updating an existing archive, a space also appears between the existing file scan and the new file scan.)  The scanning files dots are not controlled by the
       -ds  dot size option, but the dots are turned off by the -q quiet option.  The -sf show files option can be used to scan for files and get the list of files
       scanned without actually processing them.

       If zip is not able to read a file, it issues a warning but continues.  See the -MM option below for more on how zip handles patterns that  are  not  matched
       and  files  that  are not readable.  If some files were skipped, a warning is issued at the end of the zip operation noting how many files were read and how
       many skipped.

       Command modes.  zip now supports two distinct types of command modes, external and internal.  The external modes (add, update, and freshen) read files  from
       the file system (as well as from an existing archive) while the internal modes (delete and copy) operate exclusively on entries in an existing archive.

       add
              Update existing entries and add new files.  If the archive does not exist create it.  This is the default mode.

       update (-u)
              Update existing entries if newer on the file system and add new files.  If the archive does not exist issue warning then create a new archive.

       freshen (-f)
              Update existing entries of an archive if newer on the file system.  Does not add new files to the archive.

       delete (-d)
              Select entries in an existing archive and delete them.

       copy (-U)
              Select entries in an existing archive and copy them to a new archive.  This new mode is similar to update but command line patterns select entries in
              the existing archive rather than files from the file system and it uses the --out option to write the resulting archive to a  new  file  rather  than
              update the existing archive, leaving the original archive unchanged.

       The  new File Sync option (-FS) is also considered a new mode, though it is similar to update.  This mode synchronizes the archive with the files on the OS,
       only replacing files in the archive if the file time or size of the OS file is different, adding new files, and deleting  entries  from  the  archive  where
       there is no matching file.  As this mode can delete entries from the archive, consider making a backup copy of the archive.

       Also see -DF for creating difference archives.

       See each option description below for details and the EXAMPLES section below for examples.

       Split archives.   zip  version  3.0  and  later can create split archives.  A split archive is a standard zip archive split over multiple files.  (Note that
       split archives are not just archives split in to pieces, as the offsets of entries are now based on the start  of  each  split.   Concatenating  the  pieces
       together  will  invalidate  these offsets, but unzip can usually deal with it.  zip will usually refuse to process such a spliced archive unless the -FF fix
       option is used to fix the offsets.)

       One use of split archives is storing a large archive on multiple removable media.  For a split archive with 20 split files the  files  are  typically  named
       (replace ARCHIVE with the name of your archive) ARCHIVE.z01, ARCHIVE.z02, ..., ARCHIVE.z19, ARCHIVE.zip.  Note that the last file is the .zip file.  In con‐
       trast, spanned archives are the original multi-disk archive generally requiring floppy disks and using volume labels to store disk  numbers.   zip  supports
       split archives but not spanned archives, though a procedure exists for converting split archives of the right size to spanned archives.  The reverse is also
       true, where each file of a spanned archive can be copied in order to files with the above names to create a split archive.

       Use -s to set the split size and create a split archive.  The size is given as a number followed optionally by one of k (kB), m (MB), g (GB), or t (TB) (the
       default  is  m).  The -sp option can be used to pause zip between splits to allow changing removable media, for example, but read the descriptions and warn‐
       ings for both -s and -sp below.

       Though zip does not update split archives, zip provides the new option -O (--output-file or --out) to allow split archives to be updated and saved in a  new
       archive.  For example,

              zip inarchive.zip foo.c bar.c --out outarchive.zip

       reads  archive  inarchive.zip, even if split, adds the files foo.c and bar.c, and writes the resulting archive to outarchive.zip.  If inarchive.zip is split
       then outarchive.zip defaults to the same split size.  Be aware that if outarchive.zip and any split files that are created with it already exist, these  are
       always overwritten as needed without warning.  This may be changed in the future.

       Unicode.   Though  the  zip  standard requires storing paths in an archive using a specific character set, in practice zips have stored paths in archives in
       whatever the local character set is.  This creates problems when an archive is created or updated on a system using one character set and then extracted  on
       another  system  using  a different character set.  When compiled with Unicode support enabled on platforms that support wide characters, zip now stores, in
       addition to the standard local path for backward compatibility, the UTF-8 translation of the path.  This provides a common universal character set for stor‐
       ing paths that allows these paths to be fully extracted on other systems that support Unicode and to match as close as possible on systems that don't.

       On Win32 systems where paths are internally stored as Unicode but represented in the local character set, it's possible that some paths will be skipped dur‐
       ing a local character set directory scan.  zip with Unicode support now can read and store these paths.  Note that Win 9x systems and FAT file systems don't
       fully support Unicode.

       Be  aware  that  console windows on Win32 and Unix, for example, sometimes don't accurately show all characters due to how each operating system switches in
       character sets for display.  However, directory navigation tools should show the correct paths if the needed fonts are loaded.

       Command line format.  This version of zip has updated command line processing and support for long options.

       Short options take the form

              -s[-][s[-]...][value][=value][ value]

       where s is a one or two character short option.  A short option that takes a value is last in an argument and anything after it is taken as the  value.   If
       the option can be negated and "-" immediately follows the option, the option is negated.  Short options can also be given as separate arguments

              -s[-][value][=value][ value] -s[-][value][=value][ value] ...

       Short options in general take values either as part of the same argument or as the following argument.  An optional = is also supported.  So

              -ttmmddyyyy

       and

              -tt=mmddyyyy

       and

              -tt mmddyyyy

       all work.  The -x and -i options accept lists of values and use a slightly different format described below.  See the -x and -i options.

       Long options take the form

              --longoption[-][=value][ value]

       where  the  option  starts  with --, has a multicharacter name, can include a trailing dash to negate the option (if the option supports it), and can have a
       value (option argument) specified by preceeding it with = (no spaces).  Values can also follow the argument.  So

              --before-date=mmddyyyy

       and

              --before-date mmddyyyy

       both work.

       Long option names can be shortened to the shortest unique abbreviation.  See the option descriptions below for which support long options.  To avoid  confu‐
       sion,  avoid  abbreviating  a  negatable option with an embedded dash ("-") at the dash if you plan to negate it (the parser would consider a trailing dash,
       such as for the option --some-option using --some- as the option, as part of the name rather than a negating dash).  This may be changed to force  the  last
       dash in --some- to be negating in the future.

OPTIONS
       -a
       --ascii
              [Systems using EBCDIC] Translate file to ASCII format.


       -A
       --adjust-sfx
              Adjust self-extracting executable archive.  A self-extracting executable archive is created by prepending the SFX stub to an existing archive. The -A
              option tells zip to adjust the entry offsets stored in the archive to take into account this "preamble" data.

       Note: self-extracting archives for the Amiga are a special case.  At present, only the Amiga port of zip is capable of adjusting or updating  these  without
       corrupting them. -J can be used to remove the SFX stub if other updates need to be made.


       -AC
       --archive-clear
              [WIN32]  Once archive is created (and tested if -T is used, which is recommended), clear the archive bits of files processed.  WARNING: Once the bits
              are cleared they are cleared.  You may want to use the -sf show files option to store the list of files processed in case the archive operation  must
              be repeated.  Also consider using the -MM must match option.  Be sure to check out -DF as a possibly better way to do incremental backups.


       -AS
       --archive-set
              [WIN32]   Only  include  files  that  have the archive bit set.  Directories are not stored when -AS is used, though by default the paths of entries,
              including directories, are stored as usual and can be used by most unzips to recreate directories.

              The archive bit is set by the operating system when a file is modified and, if used with -AC, -AS can provide an incremental backup capability.  How‐
              ever,  other applications can modify the archive bit and it may not be a reliable indicator of which files have changed since the last archive opera‐
              tion.  Alternative ways to create incremental backups are using -t to use file dates, though this won't catch old files copied to  directories  being
              archived, and -DF to create a differential archive.


       -B
       --binary
              [VM/CMS and MVS] force file to be read binary (default is text).


       -Bn    [TANDEM] set Edit/Enscribe formatting options with n defined as
              bit  0: Don't add delimiter (Edit/Enscribe)
              bit  1: Use LF rather than CR/LF as delimiter (Edit/Enscribe)
              bit  2: Space fill record to maximum record length (Enscribe)
              bit  3: Trim trailing space (Enscribe)
              bit  8: Force 30K (Expand) large read for unstructured files


       -b path
       --temp-path path
              Use the specified path for the temporary zip archive. For example:

                     zip -b /tmp stuff *

              will  put  the  temporary  zip  archive  in the directory /tmp, copying over stuff.zip to the current directory when done. This option is useful when
              updating an existing archive and the file system containing this old archive does not have enough space to hold both old and new archives at the same
              time.   It  may also be useful when streaming in some cases to avoid the need for data descriptors.  Note that using this option may require zip take
              additional time to copy the archive file when done to the destination file system.


       -c
       --entry-comments
              Add one-line comments for each file.  File operations (adding, updating) are done first, and the user is then prompted for  a  one-line  comment  for
              each file.  Enter the comment followed by return, or just return for no comment.


       -C
       --preserve-case
              [VMS]  Preserve case all on VMS.  Negating this option (-C-) downcases.


       -C2
       --preserve-case-2
              [VMS]  Preserve case ODS2 on VMS.  Negating this option (-C2-) downcases.


       -C5
       --preserve-case-5
              [VMS]  Preserve case ODS5 on VMS.  Negating this option (-C5-) downcases.


       -d
       --delete
              Remove (delete) entries from a zip archive.  For example:

                     zip -d foo foo/tom/junk foo/harry/\* \*.o

              will  remove  the  entry  foo/tom/junk,  all of the files that start with foo/harry/, and all of the files that end with .o (in any path).  Note that
              shell pathname expansion has been inhibited with backslashes, so that zip can see the asterisks, enabling zip to match on the contents of the zip ar‐
              chive  instead of the contents of the current directory.  (The backslashes are not used on MSDOS-based platforms.)  Can also use quotes to escape the
              asterisks as in

                     zip -d foo foo/tom/junk "foo/harry/*" "*.o"

              Not escaping the asterisks on a system where the shell expands wildcards could result in the asterisks being converted to a list of files in the cur‐
              rent directory and that list used to delete entries from the archive.

              Under  MSDOS,  -d  is  case  sensitive when it matches names in the zip archive.  This requires that file names be entered in upper case if they were
              zipped by PKZIP on an MSDOS system.  (We considered making this case insensitive on systems where paths were case insensitive, but it is possible the
              archive  came from a system where case does matter and the archive could include both Bar and bar as separate files in the archive.)  But see the new
              option -ic to ignore case in the archive.


       -db
       --display-bytes
              Display running byte counts showing the bytes zipped and the bytes to go.


       -dc
       --display-counts
              Display running count of entries zipped and entries to go.


       -dd
       --display-dots
              Display dots while each entry is zipped (except on ports that have their own progress indicator).  See -ds below for setting dot size.   The  default
              is  a dot every 10 MB of input file processed.  The -v option also displays dots (previously at a much higher rate than this but now -v also defaults
              to 10 MB) and this rate is also controlled by -ds.


       -df
       --datafork
              [MacOS] Include only data-fork of files zipped into the archive.  Good for exporting files to  foreign  operating-systems.   Resource-forks  will  be
              ignored at all.


       -dg
       --display-globaldots
              Display progress dots for the archive instead of for each file.  The command

                         zip -qdgds 10m

              will turn off most output except dots every 10 MB.


       -ds size
       --dot-size size
              Set amount of input file processed for each dot displayed.  See -dd to enable displaying dots.  Setting this option implies -dd.  Size is in the for‐
              mat nm where n is a number and m is a multiplier.  Currently m can be k (KB), m (MB), g (GB), or t (TB), so if n is 100 and m is  k,  size  would  be
              100k which is 100 KB.  The default is 10 MB.

              The -v option also displays dots and now defaults to 10 MB also.  This rate is also controlled by this option.  A size of 0 turns dots off.

              This option does not control the dots from the "Scanning files" message as zip scans for input files.  The dot size for that is fixed at 2 seconds or
              a fixed number of entries, whichever is longer.


       -du
       --display-usize
              Display the uncompressed size of each entry.


       -dv
       --display-volume
              Display the volume (disk) number each entry is being read from, if reading an existing archive, and being written to.


       -D
       --no-dir-entries
              Do not create entries in the zip archive for directories.  Directory entries are created by default so that their attributes can be saved in the  zip
              archive.  The environment variable ZIPOPT can be used to change the default options. For example under Unix with sh:

                     ZIPOPT="-D"; export ZIPOPT

              (The  variable ZIPOPT can be used for any option, including -i and -x using a new option format detailed below, and can include several options.) The
              option -D is a shorthand for -x "*/" but the latter previously could not be set as default in the ZIPOPT environment  variable  as  the  contents  of
              ZIPOPT gets inserted near the beginning of the command line and the file list had to end at the end of the line.

              This version of zip does allow -x and -i options in ZIPOPT if the form

               -x file file ... @

              is used, where the @ (an argument that is just @) terminates the list.


       -DF
       --difference-archive
              Create  an archive that contains all new and changed files since the original archive was created.  For this to work, the input file list and current
              directory must be the same as during the original zip operation.

              For example, if the existing archive was created using

                     zip -r foofull .

              from the bar directory, then the command

                     zip -r foofull . -DF --out foonew

              also from the bar directory creates the archive foonew with just the files not in foofull and the files where the size or file time of the  files  do
              not match those in foofull.

              Note that the timezone environment variable TZ should be set according to the local timezone in order for this option to work correctly.  A change in
              timezone since the original archive was created could result in no times matching and all files being included.

              A possible approach to backing up a directory might be to create a normal archive of the contents of the directory as a full backup,  then  use  this
              option to create incremental backups.


       -e
       --encrypt
              Encrypt  the contents of the zip archive using a password which is entered on the terminal in response to a prompt (this will not be echoed; if stan‐
              dard error is not a tty, zip will exit with an error).  The password prompt is repeated to save the user from typing errors.


       -E
       --longnames
              [OS/2] Use the .LONGNAME Extended Attribute (if found) as filename.


       -f
       --freshen
              Replace (freshen) an existing entry in the zip archive only if it has been modified more recently than the version already in the zip archive; unlike
              the update option (-u) this will not add files that are not already in the zip archive.  For example:

                     zip -f foo

              This  command  should be run from the same directory from which the original zip command was run, since paths stored in zip archives are always rela‐
              tive.

              Note that the timezone environment variable TZ should be set according to the local timezone in order for the -f, -u and  -o  options  to  work  cor‐
              rectly.

              The  reasons  behind  this are somewhat subtle but have to do with the differences between the Unix-format file times (always in GMT) and most of the
              other operating systems (always local time) and the necessity to compare the two.  A typical TZ value is ``MET-1MEST''  (Middle  European  time  with
              automatic adjustment for ``summertime'' or Daylight Savings Time).

              The format is TTThhDDD, where TTT is the time zone such as MET, hh is the difference between GMT and local time such as -1 above, and DDD is the time
              zone when daylight savings time is in effect.  Leave off the DDD if there is no daylight savings time.  For the US Eastern time zone EST5EDT.


       -F
       --fix
       -FF
       --fixfix
              Fix the zip archive. The -F option can be used if some portions of the archive are missing, but requires a reasonably intact central directory.   The
              input  archive  is  scanned as usual, but zip will ignore some problems.  The resulting archive should be valid, but any inconsistent entries will be
              left out.

              When doubled as in -FF, the archive is scanned from the beginning and zip scans for special signatures to identify the  limits  between  the  archive
              members. The single -F is more reliable if the archive is not too much damaged, so try this option first.

              If the archive is too damaged or the end has been truncated, you must use -FF.  This is a change from zip 2.32, where the -F option is able to read a
              truncated archive.  The -F option now more reliably fixes archives with minor damage and the -FF option is needed to fix archives where -F might have
              been sufficient before.

              Neither option will recover archives that have been incorrectly transferred in ascii mode instead of binary. After the repair, the -t option of unzip
              may show that some files have a bad CRC. Such files cannot be recovered; you can remove them from the archive using the -d option of zip.

              Note that -FF may have trouble fixing archives that include an embedded zip archive that was stored (without compression) in the archive and, depend‐
              ing on the damage, it may find the entries in the embedded archive rather than the archive itself.  Try -F first as it does not have this problem.

              The format of the fix commands have changed.  For example, to fix the damaged archive foo.zip,

                     zip -F foo --out foofix

              tries  to  read the entries normally, copying good entries to the new archive foofix.zip.  If this doesn't work, as when the archive is truncated, or
              if some entries you know are in the archive are missed, then try

                     zip -FF foo --out foofixfix

              and compare the resulting archive to the archive created by -F.  The -FF option may create an inconsistent archive.  Depending on  what  is  damaged,
              you can then use the -F option to fix that archive.

              A  split  archive with missing split files can be fixed using -F if you have the last split of the archive (the .zip file).  If this file is missing,
              you must use -FF to fix the archive, which will prompt you for the splits you have.

              Currently the fix options can't recover entries that have a bad checksum or are otherwise damaged.


       -FI
       --fifo [Unix]  Normally zip skips reading any FIFOs (named pipes) encountered, as zip can hang if the FIFO is not being fed.  This option tells zip to  read
              the contents of any FIFO it finds.


       -FS
       --filesync
              Synchronize  the  contents  of  an  archive with the files on the OS.  Normally when an archive is updated, new files are added and changed files are
              updated but files that no longer exist on the OS are not deleted from the archive.  This option enables a new mode that checks entries in the archive
              against  the  file system.  If the file time and file size of the entry matches that of the OS file, the entry is copied from the old archive instead
              of being read from the file system and compressed.  If the OS file has changed, the entry is read and compressed as usual.  If the entry in  the  ar‐
              chive  does  not  match  a  file on the OS, the entry is deleted.  Enabling this option should create archives that are the same as new archives, but
              since existing entries are copied instead of compressed, updating an existing archive with -FS can be much faster than creating a new archive.   Also
              consider using -u for updating an archive.

              For this option to work, the archive should be updated from the same directory it was created in so the relative paths match.  If few files are being
              copied from the old archive, it may be faster to create a new archive instead.

              Note that the timezone environment variable TZ should be set according to the local timezone in order for this option to work correctly.  A change in
              timezone since the original archive was created could result in no times matching and recompression of all files.

              This  option  deletes files from the archive.  If you need to preserve the original archive, make a copy of the archive first or use the --out option
              to output the updated archive to a new file.  Even though it may be slower, creating a new archive with a new archive  name  is  safer,  avoids  mis‐
              matches between archive and OS paths, and is preferred.


       -g
       --grow
              Grow (append to) the specified zip archive, instead of creating a new one. If this operation fails, zip attempts to restore the archive to its origi‐
              nal state. If the restoration fails, the archive might become corrupted. This option is ignored when there's no existing archive or when at least one
              archive member must be updated or deleted.


       -h
       -?
       --help
              Display the zip help information (this also appears if zip is run with no arguments).


       -h2
       --more-help
              Display extended help including more on command line format, pattern matching, and more obscure options.


       -i files
       --include files
              Include only the specified files, as in:

                     zip -r foo . -i \*.c

              which will include only the files that end in .c in the current directory and its subdirectories. (Note for PKZIP users: the equivalent command is

                     pkzip -rP foo *.c

              PKZIP  does  not  allow recursion in directories other than the current one.)  The backslash avoids the shell filename substitution, so that the name
              matching is performed by zip at all directory levels.  [This is for Unix and other systems where \  escapes the next character.   For  other  systems
              where the shell does not process * do not use \ and the above is

                     zip -r foo . -i *.c

              Examples are for Unix unless otherwise specified.]  So to include dir, a directory directly under the current directory, use

                     zip -r foo . -i dir/\*

              or

                     zip -r foo . -i "dir/*"

              to match paths such as dir/a and dir/b/file.c [on ports without wildcard expansion in the shell such as MSDOS and Windows

                     zip -r foo . -i dir/*

              is used.]  Note that currently the trailing / is needed for directories (as in

                     zip -r foo . -i dir/

              to include directory dir).

              The long option form of the first example is

                     zip -r foo . --include \*.c

              and does the same thing as the short option form.

              Though  the  command  syntax used to require -i at the end of the command line, this version actually allows -i (or --include) anywhere.  The list of
              files terminates at the next argument starting with -, the end of the command line, or the list terminator @ (an argument that is just  @).   So  the
              above can be given as

                     zip -i \*.c @ -r foo .

              for example.  There must be a space between the option and the first file of a list.  For just one file you can use the single value form

                     zip -i\*.c -r foo .

              (no space between option and value) or

                     zip --include=\*.c -r foo .

              as  additional  examples.   The  single value forms are not recommended because they can be confusing and, in particular, the -ifile format can cause
              problems if the first letter of file combines with i to form a two-letter option starting with i.  Use -sc to see  how  your  command  line  will  be
              parsed.

              Also possible:

                     zip -r foo  . -i@include.lst

              which will only include the files in the current directory and its subdirectories that match the patterns in the file include.lst.

              Files to -i and -x are patterns matching internal archive paths.  See -R for more on patterns.


       -I
       --no-image
              [Acorn  RISC  OS] Don't scan through Image files.  When used, zip will not consider Image files (eg. DOS partitions or Spark archives when SparkFS is
              loaded) as directories but will store them as single files.

              For example, if you have SparkFS loaded, zipping a Spark archive will result in a zipfile containing a directory (and its content)  while  using  the
              'I'  option will result in a zipfile containing a Spark archive. Obviously this second case will also be obtained (without the 'I' option) if SparkFS
              isn't loaded.


       -ic
       --ignore-case
              [VMS, WIN32] Ignore case when matching archive entries.  This option is only available on systems where the case of files  is  ignored.   On  systems
              with case-insensitive file systems, case is normally ignored when matching files on the file system but is not ignored for -f (freshen), -d (delete),
              -U (copy), and similar modes when matching against archive entries (currently -f ignores case on VMS) because archive entries  can  be  from  systems
              where  case  does  matter  and  names that are the same except for case can exist in an archive.  The -ic option makes all matching case insensitive.
              This can result in multiple archive entries matching a command line pattern.


       -j
       --junk-paths
              Store just the name of a saved file (junk the path), and do not store directory names. By default, zip will store the full path (relative to the cur‐
              rent directory).


       -jj
       --absolute-path
              [MacOS] record Fullpath (+ Volname). The complete path including volume will be stored. By default the relative path will be stored.


       -J
       --junk-sfx
              Strip any prepended data (e.g. a SFX stub) from the archive.

       -k
       --DOS-names
              Attempt  to  convert  the names and paths to conform to MSDOS, store only the MSDOS attribute (just the user write attribute from Unix), and mark the
              entry as made under MSDOS (even though it was not); for compatibility with PKUNZIP under MSDOS which cannot handle certain names such as  those  with
              two dots.

       -l
       --to-crlf
              Translate the Unix end-of-line character LF into the MSDOS convention CR LF. This option should not be used on binary files.  This option can be used
              on Unix if the zip file is intended for PKUNZIP under MSDOS. If the input files already contain CR LF, this option adds  an  extra  CR.  This  is  to
              ensure  that  unzip -a on Unix will get back an exact copy of the original file, to undo the effect of zip -l.  See -ll for how binary files are han‐
              dled.

       -la
       --log-append
              Append to existing logfile.  Default is to overwrite.

       -lf logfilepath
       --logfile-path logfilepath
              Open a logfile at the given path.  By default any existing file at that location is overwritten, but the -la option will result in an  existing  file
              being opened and the new log information appended to any existing information.  Only warnings and errors are written to the log unless the -li option
              is also given, then all information messages are also written to the log.

       -li
       --log-info
              Include information messages, such as file names being zipped, in the log.  The default is to only include the command line, any warnings and errors,
              and the final status.

       -ll
       --from-crlf
              Translate  the  MSDOS  end-of-line  CR LF into Unix LF.  This option should not be used on binary files.  This option can be used on MSDOS if the zip
              file is intended for unzip under Unix.  If the file is converted and the file is later determined to be binary a warning is issued and  the  file  is
              probably  corrupted.  In this release if -ll detects binary in the first buffer read from a file, zip now issues a warning and skips line end conver‐
              sion on the file.  This check seems to catch all binary files tested, but the original check remains and if a converted file is later  determined  to
              be  binary  that warning is still issued.  A new algorithm is now being used for binary detection that should allow line end conversion of text files
              in UTF-8 and similar encodings.

       -L
       --license
              Display the zip license.

       -m
       --move
              Move the specified files into the zip archive; actually, this deletes the target directories/files after making  the  specified  zip  archive.  If  a
              directory  becomes  empty  after removal of the files, the directory is also removed. No deletions are done until zip has created the archive without
              error.  This is useful for conserving disk space, but is potentially dangerous so it is recommended to use it in combination with -T to test the  ar‐
              chive before removing all input files.

       -MM
       --must-match
              All input patterns must match at least one file and all input files found must be readable.  Normally when an input pattern does not match a file the
              "name not matched" warning is issued and when an input file has been found but later is missing or not readable a missing or not readable warning  is
              issued.   In  either  case  zip  continues  creating the archive, with missing or unreadable new files being skipped and files already in the archive
              remaining unchanged.  After the archive is created, if any files were not readable zip returns the OPEN error code (18 on most  systems)  instead  of
              the  normal  success return (0 on most systems).  With -MM set, zip exits as soon as an input pattern is not matched (whenever the "name not matched"
              warning would be issued) or when an input file is not readable.  In either case zip exits with an OPEN error and no archive is created.

              This option is useful when a known list of files is to be zipped so any missing or unreadable files will result in an error.  It is less useful  when
              used  with wildcards, but zip will still exit with an error if any input pattern doesn't match at least one file and if any matched files are unread‐
              able.  If you want to create the archive anyway and only need to know if files were skipped, don't use -MM and just check the return code.  Also  -lf
              could be useful.

       -n suffixes
       --suffixes suffixes
              Do  not  attempt  to compress files named with the given suffixes.  Such files are simply stored (0% compression) in the output zip file, so that zip
              doesn't waste its time trying to compress them.  The suffixes are separated by either colons or semicolons.  For example:

                     zip -rn .Z:.zip:.tiff:.gif:.snd  foo foo

              will copy everything from foo into foo.zip, but will store any files that end in .Z, .zip, .tiff, .gif, or  .snd  without  trying  to  compress  them
              (image  and  sound  files often have their own specialized compression methods).  By default, zip does not compress files with extensions in the list
              .Z:.zip:.zoo:.arc:.lzh:.arj.  Such files are stored directly in the output archive.  The environment variable  ZIPOPT  can  be  used  to  change  the
              default options. For example under Unix with csh:

                     setenv ZIPOPT "-n .gif:.zip"

              To attempt compression on all files, use:

                     zip -n : foo

              The maximum compression option -9 also attempts compression on all files regardless of extension.

              On Acorn RISC OS systems the suffixes are actually filetypes (3 hex digit format). By default, zip does not compress files with filetypes in the list
              DDC:D96:68E (i.e. Archives, CFS files and PackDir files).

       -nw
       --no-wild
              Do not perform internal wildcard processing (shell processing of wildcards is still done by the shell unless the arguments are escaped).  Useful if a
              list of paths is being read and no wildcard substitution is desired.

       -N
       --notes
              [Amiga,  MacOS]  Save Amiga or MacOS filenotes as zipfile comments. They can be restored by using the -N option of unzip. If -c is used also, you are
              prompted for comments only for those files that do not have filenotes.

       -o
       --latest-time
              Set the "last modified" time of the zip archive to the latest (oldest) "last modified" time found among the entries in the zip archive.  This can  be
              used without any other operations, if desired.  For example:

              zip -o foo

              will change the last modified time of foo.zip to the latest time of the entries in foo.zip.

       -O output-file
       --output-file output-file
              Process  the  archive  changes as usual, but instead of updating the existing archive, output the new archive to output-file.  Useful for updating an
              archive without changing the existing archive and the input archive must be a different file than the output archive.

              This option can be used to create updated split archives.  It can also be used with -U to copy entries from an existing archive  to  a  new  archive.
              See the EXAMPLES section below.

              Another  use  is converting zip files from one split size to another.  For instance, to convert an archive with 700 MB CD splits to one with 2 GB DVD
              splits, can use:

                     zip -s 2g cd-split.zip --out dvd-split.zip

              which uses copy mode.  See -U below.  Also:

                     zip -s 0 split.zip --out unsplit.zip

              will convert a split archive to a single-file archive.

              Copy mode will convert stream entries (using data descriptors and which should be compatible with most unzips) to normal  entries  (which  should  be
              compatible with all unzips), except if standard encryption was used.  For archives with encrypted entries, zipcloak will decrypt the entries and con‐
              vert them to normal entries.

       -p
       --paths
              Include relative file paths as part of the names of files stored in the archive.  This is the default.  The -j option junks the paths and just stores
              the names of the files.

       -P password
       --password password
              Use  password to encrypt zipfile entries (if any).  THIS IS INSECURE!  Many multi-user operating systems provide ways for any user to see the current
              command line of any other user; even on stand-alone systems there is always the threat of over-the-shoulder peeking.  Storing the plaintext  password
              as part of a command line in an automated script is even worse.  Whenever possible, use the non-echoing, interactive prompt to enter passwords.  (And
              where security is truly important, use strong encryption such as Pretty Good Privacy instead of the relatively weak standard encryption  provided  by
              zipfile utilities.)

       -q
       --quiet
              Quiet mode; eliminate informational messages and comment prompts.  (Useful, for example, in shell scripts and background tasks).

       -Qn
       --Q-flag n
              [QDOS] store information about the file in the file header with n defined as
              bit  0: Don't add headers for any file
              bit  1: Add headers for all files
              bit  2: Don't wait for interactive key press on exit

       -r
       --recurse-paths
              Travel the directory structure recursively; for example:

                     zip -r foo.zip foo

              or more concisely

                     zip -r foo foo

              In  this case, all the files and directories in foo are saved in a zip archive named foo.zip, including files with names starting with ".", since the
              recursion does not use the shell's file-name substitution mechanism.  If you wish to include only a specific subset of the files in directory foo and
              its  subdirectories,  use the -i option to specify the pattern of files to be included.  You should not use -r with the name ".*", since that matches
              ".."  which will attempt to zip up the parent directory (probably not what was intended).

              Multiple source directories are allowed as in

                     zip -r foo foo1 foo2

              which first zips up foo1 and then foo2, going down each directory.

              Note that while wildcards to -r are typically resolved while recursing down directories in the file system, any -R, -x, and -i wildcards are  applied
              to  internal archive pathnames once the directories are scanned.  To have wildcards apply to files in subdirectories when recursing on Unix and simi‐
              lar systems where the shell does wildcard substitution, either escape all wildcards or put all arguments with wildcards in quotes.  This lets zip see
              the wildcards and match files in subdirectories using them as it recurses.

       -R
       --recurse-patterns
              Travel the directory structure recursively starting at the current directory; for example:

                     zip -R foo "*.c"

              In  this  case,  all the files matching *.c in the tree starting at the current directory are stored into a zip archive named foo.zip.  Note that *.c
              will match file.c, a/file.c and a/b/.c.  More than one pattern can be listed as separate arguments.  Note for PKZIP users: the equivalent command is

                     pkzip -rP foo *.c

              Patterns are relative file paths as they appear in the archive, or will after zipping, and can have optional wildcards in them.  For  example,  given
              the current directory is foo and under it are directories foo1 and foo2 and in foo1 is the file bar.c,

                     zip -R foo/*

              will zip up foo, foo/foo1, foo/foo1/bar.c, and foo/foo2.

                     zip -R */bar.c

              will zip up foo/foo1/bar.c.  See the note for -r on escaping wildcards.


       -RE
       --regex
              [WIN32]   Before zip 3.0, regular expression list matching was enabled by default on Windows platforms.  Because of confusion resulting from the need
              to escape "[" and "]" in names, it is now off by default for Windows so "[" and "]" are just normal characters in  names.   This  option  enables  []
              matching again.


       -s splitsize
       --split-size splitsize
              Enable  creating  a split archive and set the split size.  A split archive is an archive that could be split over many files.  As the archive is cre‐
              ated, if the size of the archive reaches the specified split size, that split is closed and the next split opened.  In general  all  splits  but  the
              last  will  be  the  split size and the last will be whatever is left.  If the entire archive is smaller than the split size a single-file archive is
              created.

              Split archives are stored in numbered files.  For example, if the output archive is named archive and three splits are required,  the  resulting  ar‐
              chive  will  be  in the three files archive.z01, archive.z02, and archive.zip.  Do not change the numbering of these files or the archive will not be
              readable as these are used to determine the order the splits are read.

              Split size is a number optionally followed by a multiplier.  Currently the number must be an integer.  The multiplier  can  currently  be  one  of  k
              (kilobytes),  m  (megabytes),  g  (gigabytes), or t (terabytes).  As 64k is the minimum split size, numbers without multipliers default to megabytes.
              For example, to create a split archive called foo with the contents of the bar directory with splits of 670 MB that might be useful  for  burning  on
              CDs, the command:

                     zip -s 670m -r foo bar

              could be used.

              Currently  the old splits of a split archive are not excluded from a new archive, but they can be specifically excluded.  If possible, keep the input
              and output archives out of the path being zipped when creating split archives.

              Using -s without -sp as above creates all the splits where foo is being written, in this case the current directory.  This  split  mode  updates  the
              splits  as the archive is being created, requiring all splits to remain writable, but creates split archives that are readable by any unzip that sup‐
              ports split archives.  See -sp below for enabling split pause mode which allows splits to be written directly to removable media.

              The option -sv can be used to enable verbose splitting and provide details of how the splitting is being done.  The -sb option can be  used  to  ring
              the bell when zip pauses for the next split destination.

              Split archives cannot be updated, but see the -O (--out) option for how a split archive can be updated as it is copied to a new archive.  A split ar‐
              chive can also be converted into a single-file archive using a split size of 0 or negating the -s option:

                     zip -s 0 split.zip --out single.zip

              Also see -U (--copy) for more on using copy mode.

       -sb
       --split-bell
              If splitting and using split pause mode, ring the bell when zip pauses for each split destination.

       -sc
       --show-command
              Show the command line starting zip as processed and exit.  The new command parser permutes the arguments, putting all options and any values  associ‐
              ated  with them before any non-option arguments.  This allows an option to appear anywhere in the command line as long as any values that go with the
              option go with it.  This option displays the command line as zip sees it, including any arguments from the environment such as from the ZIPOPT  vari‐
              able.  Where allowed, options later in the command line can override options earlier in the command line.

       -sf
       --show-files
              Show  the files that would be operated on, then exit.  For instance, if creating a new archive, this will list the files that would be added.  If the
              option is negated, -sf-, output only to an open log file.  Screen display is not recommended for large lists.

       -so
       --show-options
              Show all available options supported by zip as compiled on the current system.  As this command  reads  the  option  table,  it  should  include  all
              options.   Each  line includes the short option (if defined), the long option (if defined), the format of any value that goes with the option, if the
              option can be negated, and a small description.  The value format can be no value, required value, optional value,  single  character  value,  number
              value, or a list of values.  The output of this option is not intended to show how to use any option but only show what options are available.

       -sp
       --split-pause
              If  splitting  is  enabled with -s, enable split pause mode.  This creates split archives as -s does, but stream writing is used so each split can be
              closed as soon as it is written and zip will pause between each split to allow changing split destination or media.

              Though this split mode allows writing splits directly to removable media, it uses stream archive format that may not  be  readable  by  some  unzips.
              Before relying on splits created with -sp, test a split archive with the unzip you will be using.

              To convert a stream split archive (created with -sp) to a standard archive see the --out option.

       -su
       --show-unicode
              As -sf, but also show Unicode version of the path if exists.

       -sU
       --show-just-unicode
              As -sf, but only show Unicode version of the path if exists, otherwise show the standard version of the path.

       -sv
       --split-verbose
              Enable various verbose messages while splitting, showing how the splitting is being done.

       -S
       --system-hidden
              [MSDOS, OS/2, WIN32 and ATARI] Include system and hidden files.
              [MacOS] Includes finder invisible files, which are ignored otherwise.

       -t mmddyyyy
       --from-date mmddyyyy
              Do  not  operate  on  files  modified prior to the specified date, where mm is the month (00-12), dd is the day of the month (01-31), and yyyy is the
              year.  The ISO 8601 date format yyyy-mm-dd is also accepted.  For example:

                     zip -rt 12071991 infamy foo

                     zip -rt 1991-12-07 infamy foo

              will add all the files in foo and its subdirectories that were last modified on or after 7 December 1991, to the zip archive infamy.zip.

       -tt mmddyyyy
       --before-date mmddyyyy
              Do not operate on files modified after or at the specified date, where mm is the month (00-12), dd is the day of the month (01-31), and yyyy  is  the
              year.  The ISO 8601 date format yyyy-mm-dd is also accepted.  For example:

                     zip -rtt 11301995 infamy foo

                     zip -rtt 1995-11-30 infamy foo

              will add all the files in foo and its subdirectories that were last modified before 30 November 1995, to the zip archive infamy.zip.

       -T
       --test
              Test the integrity of the new zip file. If the check fails, the old zip file is unchanged and (with the -m option) no input files are removed.

       -TT cmd
       --unzip-command cmd
              Use  command  cmd  instead  of  'unzip -tqq' to test an archive when the -T option is used.  On Unix, to use a copy of unzip in the current directory
              instead of the standard system unzip, could use:

               zip archive file1 file2 -T -TT "./unzip -tqq"

              In cmd, {} is replaced by the name of the temporary archive, otherwise the name of the archive is appended to the end of  the  command.   The  return
              code is checked for success (0 on Unix).

       -u
       --update
              Replace  (update)  an  existing entry in the zip archive only if it has been modified more recently than the version already in the zip archive.  For
              example:

                     zip -u stuff *

              will add any new files in the current directory, and update any files which have been modified since the zip archive stuff.zip was last created/modi‐
              fied (note that zip will not try to pack stuff.zip into itself when you do this).

              Note that the -u option with no input file arguments acts like the -f (freshen) option.

       -U
       --copy-entries
              Copy  entries  from  one  archive to another.  Requires the --out option to specify a different output file than the input archive.  Copy mode is the
              reverse of -d delete.  When delete is being used with --out, the selected entries are deleted from the archive and all other entries  are  copied  to
              the  new  archive, while copy mode selects the files to include in the new archive.  Unlike -u update, input patterns on the command line are matched
              against archive entries only and not the file system files.  For instance,

                     zip inarchive "*.c" --copy --out outarchive

              copies entries with names ending in .c from inarchive to outarchive.  The wildcard must be escaped on some systems to prevent the shell from  substi‐
              tuting names of files from the file system which may have no relevance to the entries in the archive.

              If no input files appear on the command line and --out is used, copy mode is assumed:

                     zip inarchive --out outarchive

              This is useful for changing split size for instance.  Encrypting and decrypting entries is not yet supported using copy mode.  Use zipcloak for that.

       -UN v
       --unicode v
              Determine what zip should do with Unicode file names.  zip 3.0, in addition to the standard file path, now includes the UTF-8 translation of the path
              if the entry path is not entirely 7-bit ASCII.  When an entry is missing the Unicode path, zip reverts back to the standard file path.   The  problem
              with  using the standard path is this path is in the local character set of the zip that created the entry, which may contain characters that are not
              valid in the character set being used by the unzip.  When zip is reading an archive, if an entry also has a Unicode path, zip now defaults  to  using
              the Unicode path to recreate the standard path using the current local character set.

              This  option  can be used to determine what zip should do with this path if there is a mismatch between the stored standard path and the stored UTF-8
              path (which can happen if the standard path was updated).  In all cases, if there is a mismatch it is assumed that the standard path is more  current
              and zip uses that.  Values for v are

                     q - quit if paths do not match

                     w - warn, continue with standard path

                     i - ignore, continue with standard path

                     n - no Unicode, do not use Unicode paths

              The default is to warn and continue.

              Characters  that  are  not valid in the current character set are escaped as #Uxxxx and #Lxxxxxx, where x is an ASCII character for a hex digit.  The
              first is used if a 16-bit character number is sufficient to represent the Unicode character and the second if the character needs more than  16  bits
              to represent it's Unicode character code.  Setting -UN to

                     e - escape

              as in

                     zip archive -sU -UN=e

              forces zip to escape all characters that are not printable 7-bit ASCII.

              Normally  zip  stores  UTF-8  directly in the standard path field on systems where UTF-8 is the current character set and stores the UTF-8 in the new
              extra fields otherwise.  The option

                     u - UTF-8

              as in

                     zip archive dir -r -UN=UTF8

              forces zip to store UTF-8 as native in the archive.  Note that storing UTF-8 directly is the default on Unix systems that support  it.   This  option
              could  be  useful  on Windows systems where the escaped path is too large to be a valid path and the UTF-8 version of the path is smaller, but native
              UTF-8 is not backward compatible on Windows systems.


       -v
       --verbose
              Verbose mode or print diagnostic version info.

              Normally, when applied to real operations, this option enables the display of a progress indicator during compression (see -dd for more on dots)  and
              requests verbose diagnostic info about zipfile structure oddities.

              However,  when  -v  is the only command line argument a diagnostic screen is printed instead.  This should now work even if stdout is redirected to a
              file, allowing easy saving of the information for sending with bug reports to Info-ZIP.  The version screen provides the help screen header with pro‐
              gram  name,  version, and release date, some pointers to the Info-ZIP home and distribution sites, and shows information about the target environment
              (compiler type and version, OS version, compilation date and the enabled optional features used to create the zip executable).

       -V
       --VMS-portable
              [VMS] Save VMS file attributes.  (Files are  truncated at EOF.)   When a -V archive is unpacked on  a  non-VMS  system,   some  file  types  (notably
              Stream_LF  text  files   and  pure binary files  like fixed-512) should be extracted intact.  Indexed files and file types with embedded record sizes
              (notably variable-length record types) will probably be seen as corrupt elsewhere.

       -VV
       --VMS-specific
              [VMS] Save VMS file attributes, and  all allocated blocks in a file,  including  any  data beyond EOF.  Useful for  moving  ill-formed  files   among
              VMS systems.   When a -VV archive is unpacked on a non-VMS system, almost all files will appear corrupt.

       -w
       --VMS-versions
              [VMS]  Append the version number of the files to the name, including multiple versions of files.  Default is to use only the most recent version of a
              specified file.

       -ww
       --VMS-dot-versions
              [VMS] Append the version number of the files to the name, including multiple versions of files, using the .nnn format.  Default is to  use  only  the
              most recent version of a specified file.

       -ws
       --wild-stop-dirs
              Wildcards match only at a directory level.  Normally zip handles paths as strings and given the paths

                     /foo/bar/dir/file1.c

                     /foo/bar/file2.c

              an input pattern such as

                     /foo/bar/*

              normally  would  match  both  paths, the * matching dir/file1.c and file2.c.  Note that in the first case a directory boundary (/) was crossed in the
              match.  With -ws no directory bounds will be included in the match, making wildcards local to a specific directory level.  So, with -ws enabled, only
              the second path would be matched.

              When using -ws, use ** to match across directory boundaries as * does normally.

       -x files
       --exclude files
              Explicitly exclude the specified files, as in:

                     zip -r foo foo -x \*.o

              which  will  include  the contents of foo in foo.zip while excluding all the files that end in .o.  The backslash avoids the shell filename substitu‐
              tion, so that the name matching is performed by zip at all directory levels.

              Also possible:

                     zip -r foo foo -x@exclude.lst

              which will include the contents of foo in foo.zip while excluding all the files that match the patterns in the file exclude.lst.

              The long option forms of the above are

                     zip -r foo foo --exclude \*.o

              and

                     zip -r foo foo --exclude @exclude.lst

              Multiple patterns can be specified, as in:

                     zip -r foo foo -x \*.o \*.c

              If there is no space between -x and the pattern, just one value is assumed (no list):

                     zip -r foo foo -x\*.o

              See -i for more on include and exclude.

       -X
       --no-extra
              Do not save extra file attributes (Extended Attributes on OS/2, uid/gid and file times on Unix).  The zip format uses extra fields to  include  addi‐
              tional  information  for each entry.  Some extra fields are specific to particular systems while others are applicable to all systems.  Normally when
              zip reads entries from an existing archive, it reads the extra fields it knows, strips the rest, and adds the extra fields applicable to that system.
              With -X, zip strips all old fields and only includes the Unicode and Zip64 extra fields (currently these two extra fields cannot be disabled).

              Negating this option, -X-, includes all the default extra fields, but also copies over any unrecognized extra fields.

       -y
       --symlinks
              For  UNIX  and  VMS (V8.3 and later), store symbolic links as such in the zip archive, instead of compressing and storing the file referred to by the
              link.  This can avoid multiple copies of files being included in the archive as zip recurses the directory trees and accesses files directly  and  by
              links.

       -z
       --archive-comment
              Prompt for a multi-line comment for the entire zip archive.  The comment is ended by a line containing just a period, or an end of file condition (^D
              on Unix, ^Z on MSDOS, OS/2, and VMS).  The comment can be taken from a file:

                     zip -z foo < foowhat

       -Z cm
       --compression-method cm
              Set the default compression method.  Currently the main methods supported by zip are store and deflate.  Compression method can be set to:

              store - Setting the compression method to store forces zip to store entries with no compression.  This is generally faster than compressing  entries,
              but results in no space savings.  This is the same as using -0 (compression level zero).

              deflate - This is the default method for zip.  If zip determines that storing is better than deflation, the entry will be stored instead.

              bzip2  -  If  bzip2 support is compiled in, this compression method also becomes available.  Only some modern unzips currently support the bzip2 com‐
              pression method, so test the unzip you will be using before relying on archives using this method (compression method 12).

              For example, to add bar.c to archive foo using bzip2 compression:

                     zip -Z bzip2 foo bar.c

              The compression method can be abbreviated:

                     zip -Zb foo bar.c

       -#
       (-0, -1, -2, -3, -4, -5, -6, -7, -8, -9)
              Regulate the speed of compression using the specified digit #, where -0 indicates no compression (store all files), -1 indicates the fastest compres‐
              sion  speed (less compression) and -9 indicates the slowest compression speed (optimal compression, ignores the suffix list). The default compression
              level is -6.

              Though still being worked, the intention is this setting will control compression speed for all compression methods.   Currently  only  deflation  is
              controlled.

       -!
       --use-privileges
              [WIN32] Use priviliges (if granted) to obtain all aspects of WinNT security.

       -@
       --names-stdin
              Take the list of input files from standard input. Only one filename per line.

       -$
       --volume-label
              [MSDOS, OS/2, WIN32] Include the volume label for the drive holding the first file to be compressed.  If you want to include only the volume label or
              to force a specific drive, use the drive name as first file name, as in:

                     zip -$ foo a: c:bar

EXAMPLES
       The simplest example:

              zip stuff *

       creates the archive stuff.zip (assuming it does not exist) and puts all the files in the current directory in it, in compressed form  (the  .zip  suffix  is
       added automatically, unless the archive name contains a dot already; this allows the explicit specification of other suffixes).

       Because of the way the shell on Unix does filename substitution, files starting with "." are not included; to include these as well:

              zip stuff .* *

       Even this will not include any subdirectories from the current directory.

       To zip up an entire directory, the command:

              zip -r foo foo

       creates the archive foo.zip, containing all the files and directories in the directory foo that is contained within the current directory.

       You  may  want  to make a zip archive that contains the files in foo, without recording the directory name, foo.  You can use the -j option to leave off the
       paths, as in:

              zip -j foo foo/*

       If you are short on disk space, you might not have enough room to hold both the original directory and the corresponding compressed zip  archive.   In  this
       case, you can create the archive in steps using the -m option.  If foo contains the subdirectories tom, dick, and harry, you can:

              zip -rm foo foo/tom
              zip -rm foo foo/dick
              zip -rm foo foo/harry

       where  the  first  command  creates foo.zip, and the next two add to it.  At the completion of each zip command, the last created archive is deleted, making
       room for the next zip command to function.




       Use -s to set the split size and create a split archive.  The size is given as a number followed optionally by one of k (kB), m (MB), g  (GB),  or  t  (TB).
       The command

              zip -s 2g -r split.zip foo

       creates  a  split  archive of the directory foo with splits no bigger than 2 GB each.  If foo contained 5 GB of contents and the contents were stored in the
       split archive without compression (to make this example simple), this would create three splits, split.z01 at 2 GB, split.z02 at 2 GB, and  split.zip  at  a
       little over 1 GB.

       The  -sp  option  can be used to pause zip between splits to allow changing removable media, for example, but read the descriptions and warnings for both -s
       and -sp below.

       Though zip does not update split archives, zip provides the new option -O (--output-file) to allow split archives to be updated and saved in a new  archive.
       For example,

              zip inarchive.zip foo.c bar.c --out outarchive.zip

       reads  archive  inarchive.zip, even if split, adds the files foo.c and bar.c, and writes the resulting archive to outarchive.zip.  If inarchive.zip is split
       then outarchive.zip defaults to the same split size.  Be aware that outarchive.zip and any split files that are created with it are always overwritten with‐
       out warning.  This may be changed in the future.





PATTERN MATCHING
       This  section applies only to Unix.  Watch this space for details on MSDOS and VMS operation.  However, the special wildcard characters * and [] below apply
       to at least MSDOS also.

       The Unix shells (sh, csh, bash, and others) normally do filename substitution (also called "globbing") on command arguments.  Generally the special  charac‐
       ters are:

       ?      match any single character

       *      match any number of characters (including none)

       []     match  any  character  in the range indicated within the brackets (example: [a-f], [0-9]).  This form of wildcard matching allows a user to specify a
              list of characters between square brackets and if any of the characters match the expression matches.  For example:

                     zip archive "*.[hc]"

              would archive all files in the current directory that end in .h or .c.

              Ranges of characters are supported:

                     zip archive "[a-f]*"

              would add to the archive all files starting with "a" through "f".

              Negation is also supported, where any character in that position not in the list matches.  Negation is supported by adding ! or ^ to the beginning of
              the list:

                     zip archive "*.[!o]"

              matches files that don't end in ".o".

              On WIN32, [] matching needs to be turned on with the -RE option to avoid the confusion that names with [ or ] have caused.


       When  these  characters  are encountered (without being escaped with a backslash or quotes), the shell will look for files relative to the current path that
       match the pattern, and replace the argument with a list of the names that matched.

       The zip program can do the same matching on names that are in the zip archive being modified or, in the case of the -x (exclude) or -i (include) options, on
       the  list of files to be operated on, by using backslashes or quotes to tell the shell not to do the name expansion.  In general, when zip encounters a name
       in the list of files to do, it first looks for the name in the file system.  If it finds it, it then adds it to the list of files to do.   If  it  does  not
       find  it,  it  looks  for the name in the zip archive being modified (if it exists), using the pattern matching characters described above, if present.  For
       each match, it will add that name to the list of files to be processed, unless this name matches one given with the -x option, or does not  match  any  name
       given with the -i option.

       The  pattern matching includes the path, and so patterns like \*.o match names that end in ".o", no matter what the path prefix is.  Note that the backslash
       must precede every special character (i.e. ?*[]), or the entire argument must be enclosed in double quotes ("").

       In general, use backslashes or double quotes for paths that have wildcards to make zip do the pattern matching for file paths,  and  always  for  paths  and
       strings that have spaces or wildcards for -i, -x, -R, -d, and -U and anywhere zip needs to process the wildcards.

ENVIRONMENT
       The following environment variables are read and used by zip as described.

       ZIPOPT
              contains default options that will be used when running zip.  The contents of this environment variable will get added to the command line just after
              the zip command.

       ZIP
              [Not on RISC OS and VMS] see ZIPOPT

       Zip$Options
              [RISC OS] see ZIPOPT

       Zip$Exts
              [RISC OS] contains extensions separated by a : that will cause native filenames with one of the specified extensions to be added to the zip file with
              basename and extension swapped.

       ZIP_OPTS
              [VMS] see ZIPOPT

SEE ALSO
       compress(1), shar(1L), tar(1), unzip(1L), gzip(1L)

DIAGNOSTICS
       The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:

              0      normal; no errors or warnings detected.

              2      unexpected end of zip file.

              3      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.

              4      zip was unable to allocate memory for one or more buffers during program initialization.

              5      a severe error in the zipfile format was detected.  Processing probably failed immediately.

              6      entry too large to be processed (such as input files larger than 2 GB when not using Zip64 or trying to read an existing archive that  is  too
                     large) or entry too large to be split with zipsplit

              7      invalid comment format

              8      zip -T failed or out of memory

              9      the user aborted zip prematurely with control-C (or similar)

              10     zip encountered an error while using a temp file

              11     read or seek error

              12     zip has nothing to do

              13     missing or empty zip file

              14     error writing to a file

              15     zip was unable to create a file to write to

              16     bad command line parameters

              18     zip could not open a specified file to read

              19     zip was compiled with options not supported on this system

       VMS  interprets standard Unix (or PC) return values as other, scarier-looking things, so zip instead maps them into VMS-style status codes.  In general, zip
       sets VMS Facility = 1955 (0x07A3), Code = 2* Unix_status, and an appropriate Severity (as specified in ziperr.h).  More details are included in the VMS-spe‐
       cific documentation.  See [.vms]NOTES.TXT and [.vms]vms_msg_gen.c.

BUGS
       zip 3.0 is not compatible with PKUNZIP 1.10. Use zip 1.1 to produce zip files which can be extracted by PKUNZIP 1.10.

       zip  files produced by zip 3.0 must not be updated by zip 1.1 or PKZIP 1.10, if they contain encrypted members or if they have been produced in a pipe or on
       a non-seekable device. The old versions of zip or PKZIP would create an archive with an incorrect format.  The old versions can list the contents of the zip
       file  but  cannot extract it anyway (because of the new compression algorithm).  If you do not use encryption and use regular disk files, you do not have to
       care about this problem.

       Under VMS, not all of the odd file formats are treated properly.  Only stream-LF format zip files are expected to work with zip.  Others  can  be  converted
       using  Rahul  Dhesi's  BILF  program.   This  version of zip handles some of the conversion internally.  When using Kermit to transfer zip files from VMS to
       MSDOS, type "set file type block" on VMS.  When transfering from MSDOS to VMS, type "set file type fixed" on VMS.   In  both  cases,  type  "set  file  type
       binary" on MSDOS.

       Under some older VMS versions, zip may hang for file specifications that use DECnet syntax foo::*.*.

       On  OS/2,  zip  cannot  match  some  names,  such  as those including an exclamation mark or a hash sign.  This is a bug in OS/2 itself: the 32-bit DosFind‐
       First/Next don't find such names.  Other programs such as GNU tar are also affected by this bug.

       Under OS/2, the amount of Extended Attributes displayed by DIR is (for compatibility) the amount returned by the 16-bit version of DosQueryPathInfo().  Oth‐
       erwise  OS/2  1.3  and 2.0 would report different EA sizes when DIRing a file.  However, the structure layout returned by the 32-bit DosQueryPathInfo() is a
       bit different, it uses extra padding bytes and link pointers (it's a linked list) to have all fields on 4-byte boundaries for  portability  to  future  RISC
       OS/2  versions.  Therefore the value reported by zip (which uses this 32-bit-mode size) differs from that reported by DIR.  zip stores the 32-bit format for
       portability, even the 16-bit MS-C-compiled version running on OS/2 1.3, so even this one shows the 32-bit-mode size.

AUTHORS
       Copyright (C) 1997-2008 Info-ZIP.

       Currently distributed under the Info-ZIP license.

       Copyright (C) 1990-1997 Mark Adler, Richard B. Wales, Jean-loup Gailly, Onno van der Linden, Kai Uwe Rommel, Igor Mandrichenko, John Bush and Paul Kienitz.

       Original copyright:

       Permission is granted to any individual or institution to use, copy, or redistribute this software so long as all of the original files are  included,  that
       it is not sold for profit, and that this copyright notice is retained.

       LIKE  ANYTHING  ELSE THAT'S FREE, ZIP AND ITS ASSOCIATED UTILITIES ARE PROVIDED AS IS AND COME WITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. IN
       NO EVENT WILL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY DAMAGES RESULTING FROM THE USE OF THIS SOFTWARE.

       Please send bug reports and comments using the web page at: www.info-zip.org.  For bug reports, please include the version of zip  (see  zip -h),  the  make
       options used to compile it (see zip -v), the machine and operating system in use, and as much additional information as possible.

ACKNOWLEDGEMENTS
       Thanks  to  R. P. Byrne for his Shrink.Pas program, which inspired this project, and from which the shrink algorithm was stolen; to Phil Katz for placing in
       the public domain the zip file format, compression format, and .ZIP filename extension, and for accepting minor changes to the file format;  to  Steve  Burg
       for  clarifications  on  the deflate format; to Haruhiko Okumura and Leonid Broukhis for providing some useful ideas for the compression algorithm; to Keith
       Petersen, Rich Wales, Hunter Goatley and Mark Adler for providing a mailing list and ftp site for the Info-ZIP group to use; and most  importantly,  to  the
       Info-ZIP  group  itself  (listed in the file infozip.who) without whose tireless testing and bug-fixing efforts a portable zip would not have been possible.
       Finally we should thank (blame) the first Info-ZIP moderator, David Kirschbaum, for getting us into this mess in the  first  place.   The  manual  page  was
       rewritten for Unix by R. P. C. Rodgers and updated by E. Gordon for zip 3.0