proof: sys-fs/diskdev_cmds/diskdev_cmds-332.14.ebuild has been installed sucessfully on a amd64 gentoo/linux system (using % ebuild diskdev_cmds-332.14.ebuild package && emerge -K diskdev_cmds ). after that in order to test it i have done: %cfdisk /dev/sde # made DOS style partition map # !NOTE: after a long ivestigation i found that it is very important to have correct TYPE set for each partiotion # cfdisk doesn't have HFS+ on it's list, googling have cleared that out - # the HFS+ has 'AF' hexidecimal code ! # i have also made a VFAT partition (which must have a correct TYPE code to work cool on mac os x # %mkfs.hfsplus -J -s -v store /dev/sde2 Initialized /dev/sde2 as a 205 GB HFS Plus volume with a 24576k journal %mkfs.vfat -n swap /dev/sde1 && sync mkfs.vfat 2.11 (12 Mar 2005) # mounting and fscking on linux worked out ( i haven't tried to write anything (just didn't have the time)) on the mac osx (panther) machine i have plugged this drive and have noticed only the FAT volume appearing - went to the diskUtility GUI and found the HFS+ one there, pressed 'verify' button and it was all fine, the volume got mounted and after i have unplagged that one an plugged back in it now shows both volumes on the desktop. i think this ebuild has definetly deserved the ~amd64 keyword. Reproducible: Always Steps to Reproduce: btw, i spend really long time having the partiotns not being recognised by the mac osx gui, how ever there very absolutely fine fsck'ing and mount'ing from the shell .. then i have came to the idea that the TYPE in fdisk has to be set exectly right.;/ it also migh be counted as a missfeature of cfdisk .. it need AF and probably someother type codes to be included !
keyworded
