unrezwack(1) [osx man page]

UNREZWACK(1)						    BSD General Commands Manual 					      UNREZWACK(1)

NAME

     /usr/bin/UnRezWack -- Split a RezWack file into separate data and resource files.

SYNOPSIS

     /usr/bin/UnRezWack file -o outFileNameBase [-f]

DESCRIPTION

     The /usr/bin/UnRezWack command takes a file created by RezWack(1) as its input file (it does not read Standard In) and divides it into two
     files, one containing the data fork and one containing the resource data.	/usr/bin/UnRezWack takes the following flags and arguments:

     file     Path to the input file.  This must be a file created with RezWack(1).

     -o outFileNameBase
	      Base path of the output files.  UnRezWack will create two files at this base path, one with the extension ".data" and one with the
	      extension ".qtr".  The resource data will be written to the data fork of the resource data file; it is not possible to create a HFS
	      or Extended HFS resource fork file using UnRezWack.

	      If either file exists, /usr/bin/UnRezWack will exit with error 2 unless the -f flag is provided.

     -f       Force overwriting of output files.

SEE ALSO

     Rez(1), DeRez(1), RezWack(1), SplitForks(1)

Mac OS X							  April 12, 2004							  Mac OS X

CPMAC(1)						    BSD General Commands Manual 						  CPMAC(1)

NAME

     /usr/bin/CpMac -- copy files preserving metadata and forks

SYNOPSIS

     /usr/bin/CpMac [-rp] [-mac] source target
     /usr/bin/CpMac [-rp] [-mac] source ... directory

DESCRIPTION

     In its first form, the /usr/bin/CpMac utility copies the contents of the file named by the source operand to the destination path named by
     the target operand.  This form is assumed when the last operand does not name an already existing directory.

     In its second form, /usr/bin/CpMac copies each file named by a source operand to a destination directory named by the directory operand.  The
     destination path for each operand is the pathname produced by the concatenation of the last operand, a slash, and the final pathname compo-
     nent of the named file.

     The following options are available:

     -r    If source designates a directory, /usr/bin/CpMac copies the directory and the entire subtree connected at that point.  This option also
	   causes symbolic links to be copied, rather than indirected through, and for /usr/bin/CpMac to create special files rather than copying
	   them as normal files.  Created directories have the same mode as the corresponding source directory, unmodified by the process' umask.

     -p    Causes /usr/bin/CpMac to preserve in the copy as many of the modification time, access time, file flags, file mode, user ID, and group
	   ID as allowed by permissions.

     -mac  Allows use of HFS-style paths for both source and target.  Path elements must be separated by colons, and the path must begin with a
	   volume name or a colon (to designate current directory).

NOTES

     The /usr/bin/CpMac command does not support the same options as the POSIX cp command, and is much less flexible in its operands.  It cannot
     be used as a direct substitute for cp in scripts.

     As of Mac OS X 10.4, the cp command preserves metadata and resource forks of files on Extended HFS volumes, so it can be used in place of
     CpMac.  The /usr/bin/CpMac command will be deprecated in future versions of Mac OS X.

SEE ALSO

     cp(1) MvMac(1)

Mac OS X							  April 12, 2004							  Mac OS X