hcopy [-m|-b|-t|-r|-a] source-path [...] target-path
hcopy transfers files from an HFS volume to UNIX or vice versa. The named source files are copied to the named destination target, which must be a directory if multiple files are to be copied.
Copies are performed using a translation mode, which must be one of:
MacBinary II: A popular format for binary file transfer. Both forks of the Macintosh file are preserved. This is the recommended mode for transferring arbitrary Macintosh files.
BinHex: An alternative format for ASCII file transfer. Both forks of the Macintosh file are preserved.
Text: Performs end-of-line translation. Only the data fork of the Macintosh file is copied.
Raw Data: Performs no translation. Only the data fork of the Macintosh file is copied.
Automatic: A mode will be chosen automatically for each file based on a set of predefined heuristics.
If no mode is specified, -a is assumed.
If a UNIX source pathname is specified as a single dash (-), hcopy will copy from standard input to the HFS destination. Likewise, a single dash used as a UNIX destination pathname will cause hcopy to copy the HFS source to standard output.
Copied files may have their filenames altered during translation. For example, an appropriate file extension may be added or removed, and certain other characters may also be transliterated.
The destination target must not be ambiguous; that is, it must be obvious whether the target is on the UNIX filesystem or on an HFS volume. As a rule, HFS targets must contain at least one colon (:), usually as the beginning of a relative pathname or by itself to represent the current working directory. To make a UNIX target unambiguous, either use an absolute pathname or precede a relative pathname with a dot and slash (./).
hfsutils(1), hls(1), hattrib(1)
Robert Leslie <firstname.lastname@example.org>
hfsutils(1), hls(1), hmount(1).