The Design and Implementation of the Anykernel and Rump Kernels

A–51
RUMP_SP(7) NetBSD Miscellaneous Information Manual RUMP_SP(7)
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 credentials 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)
NetBSD 5.99.48 February 7, 2011 NetBSD 5.99.48