In reply to Rick Moen's flatulent wordings,
> Depending on how maintainable the code is. Remember, getting
> microkernel-based systems to function reliably and well is tricky,
> and may well have been a rare, talented (and stubborn!) accomplishment
> of a small team who happen to work exactly the right way. Having that
> already accomplished in a codebase's existing state is a major win, but
> one that could be lost if a surrounding community of coders had
> difficulty keeping it that way, as it is further developed.
That wouldn't be a problem if it wasn't open sourced then, or if it was
made more restrictive so you can't read the source but the microkernel
API was well documented
> I think it clear that any sufficiently in-depth course should cover at
> least one of the following:
>> {Free|Net|Open}BSD
> Apple Darwin
> {Linux|mklinux|minix} <== note microkernels
> Unix Version 6, via the Lions book and Caldera-provided USL code
Personally I'd only choose minix out of those, because that's its
purpose, to act as as an educational but functional OS, but I'm
repeating myself so I'll stop here
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
