HFS + / HFS for Linux (SuSE)
May involve a short tutorial here how to make a MacOS file system under Linux writable. The most marked perhaps the simple commands in order to mount HFS + disks in Linux.
In Linux:
- Terminal / console open
- Enter the following command (adjust course syntax before):
mount -t hfsplus /dev/IHR_HFS_GERÄT /DER_GEWÜNSCHTE_MOUNT_PUNKT appropriate kernel modules for "hfsplus" are already installed by default in SuSE
The problem has been that these shares were only read-only. How do you get the full write access in Linux you can find below!
You must disable ledigtlich the Journal of the HFS +. This is easy to follow ...
in MacOSX:
- Open Terminal (under "Utilities")
- the following command:
sudo diskutil disableJournal /Volume/MOUNTPOINT 
MacOSX and Linux are both remote Unix derivatives and therefore used the same form of user rights. Therefore, there may be a conflict with the user rights. Because users and groups in Linux is different (UID & GID are different), you probably do not have write permission.
What to do? The plates f course, writable by all!
in MacOSX:
- Open Finder and go to said HD
- Open the "Information" (CMD + i)
- (Maybe the HD user management unlock - click the little padlock)
- File permissions for "everyone" to "Read & Write" change
The button with the gear wheel allows you to set recursively to all child directories apply.
Now the plate can be used in barrier-free Linux system. (Using the above mount command) Read Write ... no problem ... more
mount -t hfsplus /dev/IHR_HFS_GERÄT /DER_GEWÜNSCHTE_MOUNT_PUNKT It may be that in the root (root) of the plate no write access, but has all the subfolders of it. (If present no problem in case of emergency)
Copyright Notice: Images: TriOS Blog
Related Articles
Linux , button , conflict , Console , Linux , Suse Linux , Linux Terminal , Mac , MacOSX , Mount , OSX , rights , lock , Sudo , SuSE , syntax , terminal , uid , Unix
Ben ™ - 30 November 2010
I recently had a problem once, and I wanted to mount an image with HFS +. Later I found out that there is an offset, which must be considered below:
After that, everything worked perfectly!
To calculate the offset of disk Imgages have to calculate the size of the 1.Zylinders:
Offset = bytes per sector * sectors per cylinder
in our example large sectors of 512 bytes are used - the cylinder sectors include 409 640
512 * 409640 = 209735680
@ Matthiasgr - 2 May 2010
I just tinker around with LVM in VirtualBox
Ben ™ - 2 May 2010
Should anyone feel the urgent desire of the Journal HFS + again to activate ... then simply enter the terminal command: