rump_syspuffs(8) [netbsd man page]

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

NAME

     rump_syspuffs -- mount a puffs file server with a userspace puffs loop

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_syspuffs file_server arguments

DESCRIPTION

     The rump_syspuffs utility can be used to mount any puffs(3) file server so that the requests are passed through the kernel puffs code in
     userspace as well.  Therefore the approximate callgraph looks a little like the following, where k and u denote code running in the kernel
     space and userspace, respectively: puffs vfs (k) -> libpuffs (u) -> p2k (u) -> puffs vfs (u) -> libpuffs (u) -> file server (u).  The
     response path is the same, but in reverse.

     In its current state, rump_syspuffs is most useful as a proof of concept for file system distribution and for developing and debugging the
     kernel portion of puffs.

EXAMPLES

     Mount a file system with sshfs:
	   rump_syspuffs mount_psshfs server.address /mnt

     Mount an ntfs file system using ntfs-3g (from pkgsrc/filesystems/fuse-ntfs-3g), set the default uid to 1323:
	   rump_syspuffs ntfs-3g -o uid=1323 /path/to/filesystem /mnt

SEE ALSO

     p2k(3), puffs(3), rump(3), puffs(4)

HISTORY

     The rump_syspuffs debugging utility first appeared in NetBSD 5.0.

BSD
								   June 9, 2009 							       BSD

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

NAME

     rump_ext2fs -- mount a ext2fs image with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_ext2fs [options] image mountpoint

DESCRIPTION

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

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

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

SEE ALSO

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

HISTORY

     The rump_ext2fs utility first appeared in NetBSD 5.0.

BSD
								 November 21, 2010							       BSD