Based on kernel version 4.16.1. Page generated on 2018-04-09 11:53 EST.
1 Note: This filesystem doesn't have a maintainer. 2 3 Macintosh HFS Filesystem for Linux 4 ================================== 5 6 HFS stands for ``Hierarchical File System'' and is the filesystem used 7 by the Mac Plus and all later Macintosh models. Earlier Macintosh 8 models used MFS (``Macintosh File System''), which is not supported, 9 MacOS 8.1 and newer support a filesystem called HFS+ that's similar to 10 HFS but is extended in various areas. Use the hfsplus filesystem driver 11 to access such filesystems from Linux. 12 13 14 Mount options 15 ============= 16 17 When 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 46 Writing to HFS Filesystems 47 ========================== 48 49 HFS is not a UNIX filesystem, thus it does not have the usual features you'd 50 expect: 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 56 HFS does on the other have the concepts of multiple forks per file. These 57 non-standard forks are represented as hidden additional files in the normal 58 filesystems namespace which is kind of a cludge and makes the semantics for 59 the 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 69 Creating HFS filesystems 70 =================================== 71 72 The hfsutils package from Robert Leslie contains a program called 73 hformat that can be used to create HFS filesystem. See 74 <http://www.mars.org/home/rob/proj/hfs/> for details. 75 76 77 Credits 78 ======= 79 80 The HFS drivers was written by Paul H. Hargrovea (hargrove@sccm.Stanford.EDU). 81 Roman Zippel (firstname.lastname@example.org) rewrote large parts of the code and brought 82 in btree routines derived from Brad Boyer's hfsplus driver.