nomarch (1) - Linux Man Pages
nomarch: extract `.arc' archives
nomarch - extract `.arc' archives
SYNOPSISnomarch [-hlptUv] [archive.arc] [match1 [match2 ... ]]
DESCRIPTIONnomarch lists, extracts, or tests `.arc' archives. (An alternate extension sometimes used was `.ark'; these work too.) This is a very outdated file format which should certainly not be used for anything new, but you may still need an extraction utility, and here it is. :-)
- give terse usage help.
- list files in archive. If verbose listings are enabled, it shows the filename, compression method, compressed/uncompressed size, date/time, and CRC; but by default, it just shows the filename, uncompressed size, and date/time.
- extract to standard output, rather than to separate files.
- test files in archive (more precisely, check file CRCs).
- use uppercase filenames; more precisely, preserve original case from archive.
- give verbose output (when used with `-l').
- the archive to operate on.
- match1 etc.
- optionally specify which archive members to list/extract/test. Those which match any of these filenames/wildcards are processed. Wildcard operators supported are shell-like `*' and `?', but don't forget to quote arguments which use these (e.g. `nomarch foo.arc '*.bar'').
EXTRACTING MULTIPLE ARCHIVESnomarch follows the `unzip'-like practice of working on only one archive per run, with further `filenames' given on the command-line actually specifying files to extract (or whatever). The easiest way to work on multiple files with nomarch is simply to run it multiple times using for; for example:
for i in *.arc; do nomarch $i; done
USING THE PROGRAM FROM EMACSEmacs's arc-mode facility lets you work with various kinds of archive file directly from the editor. Making it use nomarch for extracting `.arc' files isn't too hard. Just add the following to your ~/.emacs file:
BUGSThe CRC used by the format is only 16-bit, so `-t' is a less-than-perfect test.
One compression method, obsolete even by `.arc' standards :-), isn't supported yet. This is partly because I've yet to find a single file which uses it, despite testing an awful lot of files.
AUTHORRussell Marks (rus [at] svgalib.org).