rump_sp(7) [netbsd man page]

RUMP_SP(7)					       BSD Miscellaneous Information Manual						RUMP_SP(7)

NAME

     rump_sp -- rump remote system call support

DESCRIPTION

     The rump_sp facility allows clients to attach to a rump kernel server over a socket and perform system calls.  While making a local rump sys-
     tem call is faster than calling the host kernel, a remote system call over a socket is slower.  This facility is therefore meant mostly for
     operations which are not performance critical, such as configuration of a rump kernel server.

   Clients
     The NetBSD base system comes with multiple preinstalled clients which can be used to configure a rump kernel and request diagnostic informa-
     tion.  These clients run as hybrids partially in the host system and partially against the rump kernel.  For example, network-related clients
     will typically avoid making any file system related system calls against the rump kernel, since it is not guaranteed that a rump network
     server has file system support.  Another example is DNS: since a rump server very rarely has a DNS service configured, host networking is
     used to do DNS lookups.

     Some examples of clients include rump.ifconfig which configures interfaces, rump.sysctl which is used to access the sysctl(7) namespace and
     rump.traceroute which is used to display a network trace starting from the rump kernel.

     Also, almost any unmodified dynamically linked application (for example telnet(1) or ls(1)) can be used as a rump kernel client with the help
     of system call hijacking.	See rumphijack(3) for more information.

   Connecting to the server
     A remote rump server is specified using an URL.  Currently two types of URLs are supported: TCP and local domain sockets.	The TCP URL is of
     the format tcp://ip.address:port/ and the local domain URL is unix://path.  The latter can accept relative or absolute paths.  Note that
     absolute paths require three leading slashes.

     To preserve the standard usage of the rump clients' counterparts the environment variable RUMP_SERVER is used to specify the server URL.  To
     keep track of which rump kernel the current shell is using, modifying the shell prompt is recommended -- this is analoguous to the visual
     clue you have when you login from one machine to another.

   Client credentials and access control
     The current scheme gives all connecting clients root credentials.	It is recommended to take precautions which prevent unauthorized access.
     For a unix domain socket it is enough to prevent access to the socket using file system permissions.  For TCP/IP sockets the only available
     means is to prevent network access to the socket with the use of firewalls.  More fine-grained access control based on cryptographic creden-
     tials may be implemented at a future date.

EXAMPLES

     Get a list of file systems supported by a rump kernel server (in case that particular server does not support file systems, an error will be
     returned):

	   $ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes

SEE ALSO

     rump_server(1), rump(3), rumpclient(3), rumphijack(3)

HISTORY

     rump_sp first appeared in NetBSD 6.0.

BSD
								 February 7, 2011							       BSD

Check Out this Related Man Page

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

NAME

     rump_msdos -- mount a msdos image with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_msdos [options] image mountpoint

DESCRIPTION

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

     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 com-
     monly 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).

SEE ALSO

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

HISTORY

     The rump_msdos utility first appeared in NetBSD 5.0.

BSD
								 November 21, 2010							       BSD

Linux and UNIX Man Pages

rump_sp(7) [netbsd man page]

Check Out this Related Man Page