On 03/06/16 09:30, Pravin wrote:
Hi,
I am trying to use the RumpKernel on Barrelfish research OS and wanted
to ask few questions in this context.
My current approach is to port the rumprun on Barrelfish by adding new
platform into rumprun. I have created simple hypervisor layer for
barrelfish platform, but I am running into problems in linking the
rumpkernel libraries with the Barrelfish application. The problem is
due to the symbol name collision in linking process as both Rumpkernel
and Barrelfish have their own libc libraries.
I wanted to check if I am missing something here and if such conflict
should not happen at-all. And what would be a clean way to handle this
conflict.
Rump kernels do not provide a libc, Rumprun does. I didn't design
Rumprun to be used for portable drivers, I did (partially) design rump
kernels for that purpose.
Is there some reason why you are not integrating just rump kernels
instead of the Rumprun stack?
