I've tested sys-fs/diskdev_cmds on ppc64 (keyword missing at the time of this report, but builds and runs anyway).
fsck.hfs and fsck.hfsplus are symlinks to fsck_hfs. This works as expected.
mkfs.hfs and mkfs.hfsplus are symlinks to newfs_hfs.
Running mkfs.hfsplus will create a hfsplus file system as expected. But running mkfs.hfs will also default to creating a hfsplus file system. It is required to add -h as a parameter, which is unexpected given the fact that mkfs.hfs should default to hfs due to its name.
Is there a way to patch nfsfs_hfs to check by which name (symlink) it was invoked and default to hfs should it be run as mkfs.hfs?
On second thought, the easy way to fix this is to add a mini shell script that will simply run newfs_hfs -h.
newfs_hfs -h $@
Is the qualitiy of this script okay?