neulab/tldr huggingface dataset:
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 mismatches 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 original 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/\*
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 current 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 handled.
-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 conversion 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 archive 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 unreadable.  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 convert 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:
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 similar 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
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 created, 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 archive 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 supports 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 archive 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 associated 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 variable.  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/modified (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 substituting 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
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
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 program 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 substitution, so that the name matching is performed by zip at all directory levels.
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
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 additional 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 compression 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 compression 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
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:
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,
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 without warning.  This may be changed in the future.
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 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]).  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.
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
compress(1), shar(1L), tar(1), unzip(1L), gzip(1L)
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-specific documentation.  See [.vms]NOTES.TXT and [.vms]vms_msg_gen.c.
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 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 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.
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.
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.
CSSLINT(1)                       csslint Manual                       CSSLINT(1)
csslint - command line CSS tool
csslint [--version | --cssom]
The csslint program parses one or more CSS files, specified on the command line as cssfile. It prints various types of output, depending upon the options selected. It is useful for detecting errors both in CSS code and in the CSS parser itself.
It is included in libcroco.
--version Display the version of libcroco used.
--cssom parse a CSS file and builds a CSS object model.
Written by Gael CHAMOULAUD (strider) <strider@freespiders.org>
Please report bugs at http://bugzilla.gnome.org.
Copyright (C) 2002-2003 Dodji SEKETELI, Gael CHAMOULAUD. This is a free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
croco-config (1)
NIKTO(1)                      Vulnerability Scanner                     NIKTO(1)
nikto - Scan web server for known vulnerabilities
/usr/local/bin/nikto [options...]
Examine a web server to find potential problems and security vulnerabilities, including:
•   Server and software misconfigurations
•   Default files and programs
•   Insecure files and programs
•   Outdated servers and programs
Nikto is built on LibWhisker (by RFP) and can run on any platform which has a Perl environment. It supports SSL, proxies, host authentication, attack encoding and more. It can be updated automatically from the command-line, and supports the optional submission of updated version data back to the maintainers.
Below are all of the Nikto command line options and explanations. A brief version of this text is available by running Nikto with the -h (-help) option.
-Cgidirs Scan these CGI directories. Special words "none" or "all" may be used to scan all CGI directories or none, (respectively). A literal value for a CGI directory such as "/cgi-test/" may be specified (must include trailing slash). If this is option is not specified, all CGI directories listed in config.txt will be tested.
-config Specify an alternative config file to use instead of the config.txt located in the install directory.
-dbcheck Check the scan databases for syntax errors.
-Display Control the output that Nikto shows. See Chapter 5 for detailed information on these options. Use the reference number or letter to specify the type, multiple may be used:
1 - Show redirects
2 - Show cookies received
3 - Show all 200/OK responses
4 - Show URLs which require authentication
D - Debug Output
V - Verbose Output
-evasion Specify the LibWhisker encoding technique to use (see the LibWhisker docs for detailed information on these). Use the reference number to specify the type, multiple may be used:
1 - Random URI encoding (non-UTF8)
2 - Directory self-reference (/./)
3 - Premature URL ending
4 - Prepend long random string
5 - Fake parameter
6 - TAB as request spacer
7 - Change the case of the URL
8 - Use Windows directory separator (\)
A - Use a carriage return (0x0d) as a request spacer
B - Use binary value 0x0b as a request spacer
-findonly Only discover the HTTP(S) ports, do not perform a security scan. This will attempt to connect with HTTP or HTTPS, and report the Server header.
-Format Save the output file specified with -o (-output) option in this format. If not specified, the default will be taken from the file extension specified in the -output option. Valid formats are:
csv - a comma-seperated list
htm - an HTML report
txt - a text report
xml - an XML report
-host Host(s) to target. Can be an IP address, hostname or text file of hosts. A single dash (-) maybe used for stdout. Can also parse nmap -oG style output
-Help Display extended help information.
-id ID and password to use for host Basic host authentication. Format is "id:password".
-list-plugins Will list all plugins that Nikto can run against targets and then will exit without performing a scan. These can be tuned for a session using the -plugins option.
The output format is:
Plugin name
full name - description
Written by author, Copyright (C) copyright