On 27/04/15 09:08, Andrew Stuart wrote:
Can you explain in a sentence/paragraph what it does? I have to admit as a
newbie to so far not seeing how it fits in to the picture fully. Perhaps a
good name will become apparent once its purpose it briefly explained.
Good question, I should've included a brief description in my mail.
The "rumpctrl" (or whatever it will be called) utilities allow remote
access to a rump kernel via various busses (*). Since a rump kernel
does not support dynamically executing processes like a regular kernel,
you can't on a whim decide to run e.g. sockstat, sysctl or ifconfig.
That's where rumpctrl comes in. You can run the commands on your
regular "control OS" (e.g. Linux), and they'll communicate the with rump
kernel reflecting and/or changing its state. If you're familiar with
Plan9, think of it as Plan9 without having to rewrite the entire OS.
If you check out this tutorial, the function will hopefully be apparent:
http://wiki.rumpkernel.org/Tutorial%3A-Getting-Started#going-remote
*) only unix local domain (not applicable for e.g. xen, since your
"control OS" does not share unix domain sockets with the rump kernel) or
tcp for now. The intent is to add support for the platform's management
bus so that public TCP is not required. It's really a simple few-day
task, but again we're a few days short of developer time ...
