RUMP_SP(7) | Miscellaneous Information Manual | RUMP_SP(7) |
rump_sp
—
rump_sp
facility allows clients to attach to a rump
kernel server over a socket and perform system calls. While making a local
rump system 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.
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.
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 analogous to
the visual clue you have when you login from one machine to another.
$ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes
rump_sp
first appeared in NetBSD
6.0.
February 7, 2011 | NetBSD 9.4 |