fixupresourceforks(1) [osx man page]

FIXUPRESOURCEFORKS(1)					    BSD General Commands Manual 				     FIXUPRESOURCEFORKS(1)

NAME

     /System/Library/CoreServices/FixupResourceForks -- Join AppleDouble files into two-fork HFS resource files.

SYNOPSIS

     /System/Library/CoreServices/FixupResourceForks [-q[uiet]] [-nosetinfo] [-nodelete] path ...

DESCRIPTION

     FixupResourceForks is to SplitForks what matter is to antimatter.	Given one or more directories that reside on an HFS or Extended HFS
     ("HFS+") volume, it scans those directories for AppleDouble files and, if found, rejoins them into two-fork resource files.  The resource
     fork data can then be accessed with normal Carbon Resource Manager calls, be processed with DeRez(1), and accessed from the POSIX file system
     interface through the ..namedfork/rsrc path mechanism.

     /System/Library/CoreServices/FixupResourceForks takes the following flags and arguments:

     -q[uiet]
	      Suppress verbose diagnostics to standard output.

     -nosetinfo
	      Do not set file system metadata (type, creator, flags, permissions) from the data in the AppleDouble file.

     -nodelete
	      Leave the AppleDouble files in the directory after copying their resource data into the resource fork of the main file.

     path ...
	      One or more directory paths.  Note that FixupResourceForks only acts on entire directories, not in individual files.

FILES

     foo     Data fork of file 'foo'

NOTES

     SplitForks will fail with error 2 if the designated file is not on an HFS or Extended HFS file system volume.

SEE ALSO

     FixupResourceForks(1), MvMac(1), CpMac(1)

STANDARDS

     Consult RFC 1740 for details on AppleSingle/AppleDouble formats.

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