p .Nm .Op options .Ar special .Ar node .Sh DESCRIPTION .Em NOTE! This manual page has been generated from a common source shared between all .Xr rump 3 file servers. Some parts of this manual page may not apply to this particular server. After reading this manual page, you may want to verify the details from .Xr mount_hfs 8 .
p The .Nm utility can be used to mount hfs file systems. It uses .Xr rump 3 and .Xr p2k 3 to facilitate running the file system as a server in userspace. As opposed to .Xr mount_hfs 8 , .Nm does not use file system code within the kernel and therefore does not require kernel support except .Xr puffs 4 . Apart from a minor speed penalty (starting from 10% and depending on the workload and file system in question), there is no difference to using in-kernel code.
p In case mounting a file system image from a regular file, .Nm does not require the use of .Xr vnconfig 8 unlike kernel file systems. Instead, the image path can be directly passed as the special file path. The exception is if the image contains a disklabel. In this case vnconfig is required to resolve the start offset for the correct partition within the image.
p It is recommended that untrusted file system images be mounted with .Nm instead of .Xr mount_hfs 8 . Corrupt file system images commonly cause the file system to crash the entire kernel, but with .Nm only the userspace server process will dump core.
p To use .Nm via .Xr mount 8 , the flags .Fl o Ar rump and .Fl t Ar hfs should be given. Similarly, .Nm is run instead of .Xr mount_hfs 8 if .Dq rump is added to the options field of .Xr fstab 5 .
p Please see .Xr mount_hfs 8 for a full description of the available command line options. .Sh SEE ALSO .Xr p2k 3 , .Xr puffs 3 , .Xr rump 3 , .Xr mount_hfs 8 .Sh HISTORY The .Nm utility first appeared in .Nx 5.0 . It is currently considered experimental.