splitforks(1) [osx man page]

SPLITFORKS(1)						    BSD General Commands Manual 					     SPLITFORKS(1)

NAME

     /usr/bin/SplitForks -- Divide a two-fork HFS file into AppleDouble format resource and data files.

SYNOPSIS

     /usr/bin/SplitForks [-s] [-v] file

DESCRIPTION

     SplitForks takes a Macintosh HFS or HFS Extended ("HFS+") two-fork file and converts it into AppleDouble format, with the data fork in one
     file and the resource fork and file system metadata in another.

     /usr/bin/SplitForks takes the following flags and arguments:

     [s]      Strip the resource fork from the original file.  The default is to leave the resource file in place after copying it to its Apple-
	      Double metadata file.

     [v]      Produce verbose diagnostics to standard output.

     file     The file to split.

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

AFILE(1)						      General Commands Manual							  AFILE(1)

NAME

       afile - display type and creator of Apple Macintosh files (netatalk format)

SYNOPSIS

       afile [ -a ] file ...

DESCRIPTION

       afile  displays	the  name  and Macintosh type and creator of the file arguments. Tests whether the file is an AppleDouble header, in which
       case it checks the corresponding data fork exists, or assumes it is a data fork in which case it looks for the corresponding AppleDouble to
       find the type/creator information.

       afile does not look at any of the extension mapping files such as AppleVolumes.system.

OPTIONS

       -a     Include directories and data files of unknown type (i.e. without corresponding AppleDouble) in output.

DIAGNOSTICS

       returns exit status 0 if all files have a corresponding valid  .AppleDouble header or data fork, or 99 for bad command line options. Other-
       wise it returns the following error code relating to the last invalid file.

       1  file doesn't exist
       2  file is unreadable
       3  file is directory
       4  file is AppleDouble without data fork
       5  file is AppleDouble with unreadable data fork
       6  file is data fork without AppleDouble
       7  file is data fork with unreadable AppleDouble
       8  file is data fork with short AppleDouble
       9  bad magic in AppleDouble

SEE ALSO

       achfile(1), afpd(1)

								    26 Feb 1998 							  AFILE(1)