On 22/08/16 11:54, Geoffrey Clements wrote:
Just for the record, the minimum list would seem to be:
-lrumpnet -lrumpnet_config -lrumpnet_net
The project I have planned for my unikernel will require networking so this is
not a problem for me.
It is definitely possible to avoid including the networking stack.
That's in fact what I did, IIRC, for rumprun-nethack. However, it
requires a bit of recompilation. Of course, it's not impossible or even
hard to fix properly, but nobody has had a pressing need to fix it and
contribute their fix for others to enjoy.
I would love to be able to contribute but, alas, I'm not sure I am capable
enough for such things.
There's only way to become capable.
It's probably straightforward hacking. Shortly, one probably should
port the relevant bits from rumpnet_config to "userspace" and include
them directly in the config part of librumprun_base. The dhcp client
should probably be a separate component. Doing so will eliminate the
linkage dependency with rumpnet_config, which will transitively
eliminate the dependency with rumpnet and rumpnet_net.
I'm saying "probably", because akin to becoming capable, there's only
one way to test if a guess is truly correct.
