hfs.txt 2.9 KB

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