Linked by Andrew Hudson on Mon 20th Jun 2011 17:19 UTC
BeOS & Derivatives Haiku Alpha 3 has been in development for more than 14 months. In that time more than 800 bugs have been identified and fixed, major sections have been updated, applications have been added and updated, and great progress has been made in supporting additional hardware. Here is a summary of updates, more details can be found here. Also inside, interviews with some core Haiku developers.
Thread beginning with comment 477963
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Looking Forward to Haiku
by senshikaze on Tue 21st Jun 2011 11:49 UTC in reply to "RE[4]: Looking Forward to Haiku"
Member since:

I always have a hard time defining hybrids myself ;) Most known hybrids sound to me like extremely modular monolithic designs : a huge lot of functionality is still in kernel mode, sharing a common address space, but in separate and easily replaceable code modules.

IANAKH(I am not a kernel hacker), but that is the way I read hybrid kernels, too. If you make that argument, then wouldn't the LKM in linux kinda be (almost) a hybrid design? It is runtime loadable drivers and subsystems. Not quite a micro kernel, but not quite a monolithic either. just right. ;)

*edit: stupid me, forgot that a microkernel design requires the pieces to be outside of kernel space. I should really pay attention when reading "OPerating Systems, Design and implementations."

Edited 2011-06-21 11:53 UTC

Reply Parent Score: 1

Neolander Member since:

Yup. I have a hard time distinguishing "modular kernel" and "hybrid kernel", but if both means the same, on which we seem to agree, then I have to say that Linux definitely qualifies as a modular kernel.

Edited 2011-06-21 13:19 UTC

Reply Parent Score: 1

Neolander Member since:

For instant fun...

Notice that Linux is in both categories, but that NT and XNU somehow escape the monolithic kernel definition.

Pictures pretty well how much blurred the lines are.

Myself, I tend to base myself on the following categorization :

Monolithic (non-modular) : Old designs. The kernel includes lots of features in an inflexible way.

Modular : Most modern desktop kernels. Still lots of stuff in the kernel space, which gives some credit to people who also classify them as monolithic, but code modules are sufficiently independent from each other that you can selectively add and remove them at run time.

Microkernels : There is an explicit intent to put every functionality which does not need full system access (as an example, the VFS) outside of the kernel.

Picokernels, nanokernels : Microkernels which want to show off.

Hybrid kernels : Modular kernels which want to show off.

Edited 2011-06-21 13:44 UTC

Reply Parent Score: 1