HCOPY(1)HCOPY(1)NAME
hcopy - copy files from or to an HFS volume
SYNOPSIS
hcopy [-m|-b|-t|-r|-a] source-path [...] target-path
DESCRIPTION
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:
-m MacBinary II: A popular format for binary file transfer. Both
forks of the Macintosh file are preserved. This is the recom‐
mended mode for transferring arbitrary Macintosh files.
-b BinHex: An alternative format for ASCII file transfer. Both
forks of the Macintosh file are preserved.
-t Text: Performs end-of-line translation. Only the data fork of
the Macintosh file is copied.
-r Raw Data: Performs no translation. Only the data fork of the
Macintosh file is copied.
-a 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.
NOTES
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 obvi‐
ous 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 cur‐
rent working directory. To make a UNIX target unambiguous, either use
an absolute pathname or precede a relative pathname with a dot and
slash (./).
SEE ALSOhfsutils(1), hls(1), hattrib(1)AUTHOR
Robert Leslie <rob@mars.org>
HFSUTILS 13-Jan-1997 HCOPY(1)