Hacker News new | ask | show | jobs
by akavel 3906 days ago
Uh, so only FS for now? That's sure nice, and a nice start, but I really thought there's more to it. Thanks for the clarification & and details.

(I remembered that Haiku got network drivers from some WhatsitBSD, so I thought those are maybe there too, but it seems it was FreeBSD actually, so just some confusion of mine. So no microkernel there, it seems. Bummer.)

As to running on Xen etc, that was what I seemed to vaguely remeber as what rump kernels mean, so I was really confused and surprised to slowly find out that the NetBSD usage of the term seems to diverge quite substantially, as far as I can (or can't?) understand. Hmph.

1 comments

I just saw this so not sure if you'll actually see this response, but rump kernel doesn't imply Xen or such, that is just a common thing people want to do with them. It just means kernel drivers that can be used outside the kernel. Anykernel refers to a kernel that can be used that way with minimal differences and without modifying individual drivers. So rump kernel is "libkernel" and an anykernel is one way to get a rump kernel.

There is a FAQ with more information at: https://github.com/rumpkernel/wiki/wiki/Info:-FAQ

I'm pretty sure that Antti created these terms, so it is an authoritative definition :).

Thanks. The problem is, I actually have already read the appropriate sections of the FAQ & some rumpkernel.org pages, but I'm still confused. (I've written my original question out of frustration that things didn't become clear after all the reading.) I'm starting to think it may be best to dive in and try reading the "book" referenced in the FAQ (i.e. the Antti's PhD paper). Seems actually very approachable for a regular non-sciency engineer, from first looks. And/or maybe the "tutorial" I've found at https://github.com/rumpkernel/wiki/wiki/Tutorial:-Getting-st...