On Sat, Oct 25, 2014 at 12:55 PM, Antti Kantee <[email protected]> wrote: >> IMO they (librumpkern_sys_foo, rumprun-*) serve different use cases. If I >> understand you correctly the rumprun-* model serves when you want to run >> unmodified applications using the entire rump kernel stack.
I think the use case of wanting to talk to rump stack and native kernel stack is as Antti says "expert" but there are use cases, eg I was talking just the other day to someone who was interested in having an application that talked to the network purely via rump but talked via sockets to other code on the box. There are namespacing issues but I think it is possible to make something where this is not too horrible, as this is essentially what rumprun is doing internally. I hope to have a proof of concept in a while... Justin ------------------------------------------------------------------------------ _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
