On 24/10/14 15:27, Martin Lucina wrote: >> I seem to recall that there's a mail in the list archives discussing the >> relative merits of syscall compat vs. rumprun, but I couldn't find a >> link with a few minutes of searching. > > I hunted through the GMANE archive back to its beginning and couldn't find > anything related either... Would be interested in understanding more about > how this works, will put on my list of code to read :-)
Ok I doubled my efforts to find the mail and actually found it. The reason you couldn't find it from gmane is because it was sent a week before the list started being archived at gmane ;) http://sourceforge.net/p/rumpkernel/mailman/message/31896738/ (perhaps check out the referenced github issue too) >> Anyway, getting back to your proposal, I think I would prefer to guide >> new users just towards rumprun, where things just magically work on any >> platform. Less explaining => better. If learning about the type >> incompat becomes necessary, it can be an expert topic. Makes sense? > > 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. You are correct, they do. And IMO one case is an expert case while the other one is the regular case. The beauty of rumprun, from a tutorial's perspective, is that it works more or less like an OS and therefore looks familiar to newcomers. By adding just a bit of extra info, we get to a point where people can do very useful things with rump kernels by using what they are already familiar with. > In the case of eg. fs-utils and also the project I've been working on where > you want to interact both natively with the host filesystem and a rump > kernel filesystem, rumprun-* does not really fit...? One could always add a /hostfs driver for that... (though, at least out of fs-utils, fsu_ecp is really the only one I remember to be accessing the host file system) Don't worry, I'm not saying syscall compat is going away. It is, however, relatively incomplete, and you don't get portable behaviour like you do with rumprun. In other words, syscall compat is a cold, surgical precision tool, not a comforting "everything just works"-blanket. ------------------------------------------------------------------------------ _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
