rump_smbfs(8) [netbsd man page]

RUMP_SMBFS(8)						    BSD System Manager's Manual 					     RUMP_SMBFS(8)

NAME

     rump_smbfs -- mount a smbfs share with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_smbfs [options] share mountpoint

DESCRIPTION

     NOTE! This manual page describes features specific to the rump(3) file server.  Please see mount_smbfs(8) for a full description of the
     available command line options.

     The rump_smbfs utility can be used to mount smbfs file systems.  It uses rump(3) and p2k(3) to facilitate running the file system as a server
     in userspace.  As opposed to mount_smbfs(8), rump_smbfs 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.

     Even though the rump_smbfs file system client runs within a virtual rump kernel in userspace, it uses host network services (by means of
     ``rump sockin'').	This means that regardless of whether using rump_smbfs or mount_smbfs(8), the same network configurations will be used.
     Currently, ``sockin'' supports IPv4.

     To use rump_smbfs via mount(8), the flags -o rump and -t smbfs should be given.  Similarly, rump_smbfs is used instead of mount_smbfs(8) if
     ``rump'' is added to the options field of fstab(5).

SEE ALSO

     p2k(3), puffs(3), rump(3), mount_smbfs(8)

HISTORY

     The rump_smbfs utility first appeared in NetBSD 6.0.

BSD
								 November 21, 2010							       BSD

RUMP_V7FS(8)						    BSD System Manager's Manual 					      RUMP_V7FS(8)

NAME

     rump_v7fs -- mount a v7fs image with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_v7fs [options] image mountpoint

DESCRIPTION

     NOTE! This manual page describes features specific to the rump(3) file server.  Please see mount_v7fs(8) for a full description of the avail-
     able command line options.

     The rump_v7fs utility can be used to mount v7fs file systems.  It uses rump(3) and p2k(3) to facilitate running the file system as a server
     in userspace.  As opposed to mount_v7fs(8), rump_v7fs 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_v7fs 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_v7fs instead of mount_v7fs(8).  Corrupt file system images commonly
     cause the file system to crash the entire kernel, but with rump_v7fs only the userspace server process will dump core.

     To use rump_v7fs via mount(8), the flags -o rump and -t v7fs should be given.  Similarly, rump_v7fs is used instead of mount_v7fs(8) if
     ``rump'' is added to the options field of fstab(5).

SEE ALSO

     p2k(3), puffs(3), rump(3), mount_v7fs(8)

HISTORY

     The rump_v7fs utility first appeared in NetBSD 6.0.

BSD
								 November 21, 2010							       BSD