Linked by Thom Holwerda on Sun 30th Sep 2007 14:00 UTC
Thread beginning with comment 275578
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-12-18
"For reference, neither BeOS nor Haiku are microkernels in any sense of the word."
BeOS is microkernelish, e.g. a hybrid kernel (though the very term hybrid kernel is probably correctly dismissed by most experts as a nonsense term), in that it implements microkernel concepts of servers, message based IPC, etc. That some claim the Amiga OS is a microkernel is just about as valid or invalid, depending on your point of view. The reality is that while Amiga OS exec does implement what would become microkernel like functionality (message passing between tasks), it doesn’t really have defined process address spaces or the ability to implement protected process based application environment servers, along with other core microkernel features. By classic compsci definitions, AmigaOS is as much a monolithic kernel as nearly everything else.
In this current era, I think the entire concept of microkernelized versus monolithic design is obsolete since both camps have borrowed so much from one another that nearly all mainstream kernel's (NT, OSX/Darwin and Linux), regardless of their origins, don't cleanly fall into either designation. Furthermore, things keep moving around (user mode driver frameworks, HTTP stack in kernel mode, etc.) so the whole discussion is really just academic at this point.