linux/Documentation/filesystems/hfs.txt
<<
>>
Prefs
   1Note: This filesystem doesn't have a maintainer.
   2
   3Macintosh HFS Filesystem for Linux
   4==================================
   5
   6HFS stands for ``Hierarchical File System'' and is the filesystem used
   7by the Mac Plus and all later Macintosh models.  Earlier Macintosh
   8models used MFS (``Macintosh File System''), which is not supported,
   9MacOS 8.1 and newer support a filesystem called HFS+ that's similar to
  10HFS but is extended in various areas.  Use the hfsplus filesystem driver
  11to access such filesystems from Linux.
  12
  13
  14Mount options
  15=============
  16
  17When mounting an HFS filesystem, the following options are accepted:
  18
  19  creator=cccc, type=cccc
  20        Specifies the creator/type values as shown by the MacOS finder
  21        used for creating new files.  Default values: '????'.
  22
  23  uid=n, gid=n
  24        Specifies the user/group that owns all files on the filesystems.
  25        Default:  user/group id of the mounting process.
  26
  27  dir_umask=n, file_umask=n, umask=n
  28        Specifies the umask used for all files , all directories or all
  29        files and directories.  Defaults to the umask of the mounting process.
  30
  31  session=n
  32        Select the CDROM session to mount as HFS filesystem.  Defaults to
  33        leaving that decision to the CDROM driver.  This option will fail
  34        with anything but a CDROM as underlying devices.
  35
  36  part=n
  37        Select partition number n from the devices.  Does only makes
  38        sense for CDROMS because they can't be partitioned under Linux.
  39        For disk devices the generic partition parsing code does this
  40        for us.  Defaults to not parsing the partition table at all.
  41
  42  quiet
  43        Ignore invalid mount options instead of complaining.
  44
  45
  46Writing to HFS Filesystems
  47==========================
  48
  49HFS is not a UNIX filesystem, thus it does not have the usual features you'd
  50expect:
  51
  52 o You can't modify the set-uid, set-gid, sticky or executable bits or the uid
  53   and gid of files.
  54 o You can't create hard- or symlinks, device files, sockets or FIFOs.
  55
  56HFS does on the other have the concepts of multiple forks per file.  These
  57non-standard forks are represented as hidden additional files in the normal
  58filesystems namespace which is kind of a cludge and makes the semantics for
  59the a little strange:
  60
  61 o You can't create, delete or rename resource forks of files or the
  62   Finder's metadata.
  63 o They are however created (with default values), deleted and renamed
  64   along with the corresponding data fork or directory.
  65 o Copying files to a different filesystem will loose those attributes
  66   that are essential for MacOS to work.
  67
  68
  69Creating HFS filesystems
  70===================================
  71
  72The hfsutils package from Robert Leslie contains a program called
  73hformat that can be used to create HFS filesystem. See
  74<http://www.mars.org/home/rob/proj/hfs/> for details.
  75
  76
  77Credits
  78=======
  79
  80The HFS drivers was written by Paul H. Hargrovea (hargrove@sccm.Stanford.EDU).
  81Roman Zippel (roman@ardistech.com) rewrote large parts of the code and brought
  82in btree routines derived from Brad Boyer's hfsplus driver.
  83
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.