man.bsd.lv manual page server

DESCRIPTION

The rump_msdos utility can be used to mount msdos file systems. It uses rump(3) and p2k(3) to facilitate running the file system as a server in userspace. As opposed to mount_msdos(8), rump_msdos 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 there is no downside with respect to in-kernel code.

rump_msdos does not require using vnconfig(8) for mounts from regular files and the file path can be passed directly as the image parameter. In fact, the use of vnconfig(8) is discouraged, since it is unable to properly deal with images on sparse files.

In case the image contains multiple partitions, the desired partition must be indicated by appending the token “%DISKLABEL:p%” to the image path. The letter “p” specifies the partition as obtained via disklabel(8). For example, to mount partition “e” from image /tmp/wd0.img, use “/tmp/wd0.img%DISKLABEL:e%”.

It is recommended that untrusted file system images be mounted with rump_msdos instead of mount_msdos(8). Corrupt file system images commonly cause the file system to crash the entire kernel, but with rump_msdos only the userspace server process will dump core.

To use rump_msdos via mount(8), the flags -o rump and -t msdos should be given. Similarly, rump_msdos is used instead of mount_msdos(8) if “rump” is added to the options field of fstab(5).