To  provide  support for Mac OS X, radmind is aware of the Mac OS meta-
       data used on HFS+-formatted drives. When lcreate uploads a file denoted
       in  the  transcript as an applefile (type 'a'), it encodes the file and
       the file's metadata to the server as an AppleSingle file. The AppleSin-
       gle  file  is an archive containing a file's relevant metadata and data
       in a single file stream. The radmind AppleSingle file has the following

       1)  The AppleSingle header, consisting of a 4-byte magic number, 4-byte
       version number, 16-byte filler, 2-byte number denoting  the  number  of
       entries in the archive, and 3 header entries, each describing the items
       in the archive and containing a 4-byte entry  id,  4-byte  offset,  and
       4-byte length;

       2)  The  file's  Finder information (32 bytes), which stores the file's
       Type and Creator codes, as well its position in the Finder window;

       3) The file's Resource Fork, which contains things like images, sounds,
       and other data not easily or appropriately stored in the Data Fork;

       4)  The  file's Data Fork, the portion visible from the Finder, and the
       only part which is considered valid by flat file systems.

       The radmind tool lapply similarly decodes the applefile from the server
       and  restores it to the client Mac OS X machine running on an HFS+-for-
       matted drive.


       The   Apple   Computer's    AppleSingle    RFC    is    available    at


       ktcheck(1),  lapply(1),  lcreate(1),  lcksum(1),  lfdiff(1), lmerge(1),
       lsort(1), radmind(8), twhich(1).


Man(1) output converted with man2html