Hello list!

Do you think it would require a lot of effort to write the necessary wrappers to
run a rump kernel as a process separate from the one that actually uses it? And
what about having one user app communicating with multiple rump kernels (each
providing different services)?

That is, something resembling the prototypical multi-server system on top of a
microkernel.

For example, a user app communicating with a process implementing the filesystem
using rump, and with another implementing the TCP/IP stack. I understand I won't
be able to run subsystems on separate processes, though (e.g., isolate the
network driver and TCP/IP stack on different processes).


Thanks a lot,
   Lluis


Reply via email to