NOTE! This manual page has been generated from a common source shared between all
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
mount_sysvbfs(8).
The
rump_sysvbfs utility can be used to mount sysvbfs file systems. It uses
rump(3) and
p2k(3) to facilitate running the file system as a server in userspace. As opposed to
mount_sysvbfs(8),
rump_sysvbfs does not use file system code within the kernel and therefore does not require kernel support except
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.
In case mounting a file system image from a regular file,
rump_sysvbfs does not require the use of
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.
It is recommended that untrusted file system images be mounted with
rump_sysvbfs instead of
mount_sysvbfs(8). Corrupt file system images commonly cause the file system to crash the entire kernel, but with
rump_sysvbfs only the userspace server process will dump core.
To use
rump_sysvbfs via
mount(8), the flags
-o rump and
-t sysvbfs should be given. Similarly,
rump_sysvbfs is run instead of
mount_sysvbfs(8) if “rump” is added to the options field of
fstab(5).
Please see
mount_sysvbfs(8) for a full description of the available command line options.