The Design and Implementation of the Anykernel and Rump Kernels

A–18
RUMP(3) NetBSD Library Functions Manual RUMP(3)
ble to load components at runtime. There are two ways of doing this:
using dlopen() to link a shared library into a rump kernel and initializing
with rump_pub_module_init() or specifying a module on the file system
to rump_sys_modctl() and letting the rump kernel do the linking.
Notably, in the latter case debugging with symbols is not possible since
the host gdb does not know about symbols loaded by the rump kernel. Generally
speaking, dynamically loadable components must follow kernel module
boundaries.
SEE ALSO
rump_server(1), p2k(3), rump_etfs(3), rump_lwproc(3), rumpclient(3),
rumphijack(3), rumpuser(3), ukfs(3), rump_sp(7)
Antti Kantee, "Environmental Independence: BSD Kernel TCP/IP in
Userspace", Proceedings of AsiaBSDCon 2009, pp. 71-80, March 2009.
Antti Kantee, "Kernel Development in Userspace - The Rump Approach",
BSDCan 2009, May 2009.
Antti Kantee, "Rump File Systems: Kernel Code Reborn", Proceedings of the
2009 USENIX Annual Technical Conference, pp. 201-214, June 2009.
Arnaud Ysmal and Antti Kantee, "Fs-utils: File Systems Access Tools for
Userland", EuroBSDCon 2009, September 2009.
Antti Kantee, "Rump Device Drivers: Shine On You Kernel Diamond",
Proceedings of AsiaBSDCon 2010, pp. 75-84, March 2010.
HISTORY
rump appeared as an experimental concept in NetBSD 5.0.
version was released in NetBSD 6.0.
The first stable
NetBSD 5.99.48 March 25, 2011 NetBSD 5.99.48