On 09/04/15 15:39, Martin Lucina wrote:
On Sunday, 05.04.2015 at 23:38, Antti Kantee wrote:
If you think the names suck, invent just better ones, and we can
change them without screwing users because they're exposed only
internally(!).
The names are fine, however the internal prefix of "bmk" in headers and
symbols is sucky. Will that change to "rumprun" eventually?
There's nothing rumprun-specific in those layers! (rumprun == unikernel
for posix applications)
Like I explained in my original email, you can toss the entire
application side of things and still have a running rump kernel on
platform X. Now, granted, that "bmk" code shouldn't be in the rumprun
repo, but I'm a bit tired with playing repo games at the moment because
pulling in submodules makes development very frustrating, so the split
will have to wait for a) "bmk" to stabilize fully b) a use case.
However, the conceptual split is there and we shouldn't dilute it by
lumping everything under one namespace, because that will make it
difficult to later figure out what actually goes where.
