On 20/04/15 03:25, BCG wrote:
That makes sense... my only question about that is, what is the status
of rumprun-posix? Is that still necessary and/or useful for testing
applications in userspace? Or should I just go straight onto
xen/baremetal?
Yes, you can theoretically use rumprun-posix for testing, though the
feature set it supports is now so diverged from rumprun(/baremetal/xen)
that testing might not reflect the reality of the target platforms. In
fact, as of late rumprun-posix only builds only the remote clients,
which still are very useful. There's intent to integrate userspace
platform support into rumprun, but that's one of those things which will
happen only when someone gets too annoyed by the lack of support.
*) we don't exactly know what that means yet, but something along the
lines of "doesn't fork and exec all over the place and doesn't assume
virtual memory"
Got it... porting is out... rumprun is in. And I will definitely do my
best to give you some meaningful feedback.
Though, like Justin noted with the null pointers, occasionally you do
have to do some modifications for things to work. I think especially
languages with garbage collection might be problematic without being
able to trap memory access violations. After testing, it's probably
best to contact upstream and try to work out if it's going to be 1) we
change 2) they change or 3) run Linux.
