manual

infozip2.2源码

	      UNIX, ^Z on MSDOS, OS/2, and VAX/VMS).  The comment
	      can be taken from a file:

		     zip -z foo < foowhat

       -#     Regulate the speed of compression using the  speci-
	      fied  digit  #,  where  -0 indicates no compression
	      (store all files), -1 indicates  the  fastest  com-
	      pression method (less compression) and -9 indicates
	      the slowest compression  method  (optimal	 compres-
	      sion,  ignores  the  suffix list). The default com-
	      pression level is -6.

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

       -$     Include  the volume label for the the drive holding
	      the first file to be compressed.	If  you	 want  to
	      include  only  the  volume label or to force a spe-
	      cific drive, use the drive name as first file name,
	      as in:

		     zip -$ foo a: c:bar

	      This  option  is	effective  on  some  systems only
	      (MSDOS and OS/2); it is ignored on Unix.

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  that  archive  name  given contains a dot already;
       this allows the explicit specification of other suffixes).

       Because	of  the way the shell 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:

Info-ZIP	       22 June 1997 (v2.2)		       11

ZIP(1L)							  ZIP(1L)

	      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 corre-
       sponding 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.

PATTERN MATCHING
       This section applies only to UNIX.  Watch this  space  for
       details on MSDOS and VMS operation.

       The  UNIX  shells (sh(1) and csh(1)) do filename substitu-
       tion on command arguments.  The special characters 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]).

       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 pat-
       tern, 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

Info-ZIP	       22 June 1997 (v2.2)		       12

ZIP(1L)							  ZIP(1L)

       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  char-
       acters  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 argu-
       ment must be enclosed in double quotes ("").

       In general, use backslash  to  make  zip	 do  the  pattern
       matching	 with  the  -f (freshen) and -d (delete) options,
       and sometimes after the -x (exclude) option when used with
       an appropriate operation (add, -u, -f, or -d).

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  imme-
		     diately.

	      6	     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 con-
		     trol-C (or similar)

	      10     zip encountered an error while using a  temp

Info-ZIP	       22 June 1997 (v2.2)		       13

ZIP(1L)							  ZIP(1L)

		     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

       VMS  interprets	standard  Unix	(or  PC) return values as
       other, scarier-looking things, so zip  instead  maps  them
       into  VMS-style	status	codes.	The current mapping is as
       follows:	  1 (success) for normal exit,
	and  (0x7fff000?  +  16*normal_zip_exit_status)	 for  all
       errors,	where  the `?' is 0 (warning) for zip value 12, 2
       (error) for the zip values 3, 6, 7, 9, 13, 16, 18,  and	4
       (fatal error) for the remaining ones.

BUGS
       zip  2.2	 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 2.2 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 Vax to MSDOS, type "set file type block" on
       the  Vax.   When	 transfering from MSDOS to Vax, type "set
       file type fixed" on the Vax.  In	 both  cases,  type  "set
       file type binary" on MSDOS.

       Under VMS, zip hangs for file specification that uses DEC-
       net syntax foo::*.*.

       On OS/2, zip  cannot  match  some  names,  such	as  those

Info-ZIP	       22 June 1997 (v2.2)		       14

ZIP(1L)							  ZIP(1L)

       including  an  exclamation mark or a hash sign.	This is a
       bug in OS/2 itself:  the	 32-bit	 DosFindFirst/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(). Otherwise	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  porta-
       bility,	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) 1990-1997	Mark  Adler,  Richard  B.  Wales,
       Jean-loup  Gailly,  Onno	 van  der Linden, Kai Uwe Rommel,
       Igor Mandrichenko, John Bush and Paul Kienitz.  Permission
       is  granted to any individual or institution to use, copy,
       or redistribute this software so long as all of the origi-
       nal  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  by  email   to:
       [e-mail].	 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  pro-
       viding 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

Info-ZIP	       22 June 1997 (v2.2)		       15

ZIP(1L)							  ZIP(1L)

       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.

Info-ZIP	       22 June 1997 (v2.2)		       16