Star Why you Shouldn't Write your Own Kernel Anymore
Linked by Emmanuel Marty on Thu 2nd Sep 2004 07:36 UTC
OSNews, Generic OSes As a programmer and manager of embedded software products for a living, I think that operating system programming is so much fun that it will eventually be outlawed. I've previously published two articles on OSNews, So, you want to write an operating system and Climbing the kernel mountain, and tried to summarize my experience in designing operating system kernels as well as technical traps that can be easily avoided.
E-mail Print r 0   · Read More · 127 Comment(s) http://osne.ws/6aq
Permalink for comment
To read all comments associated with this story, please click here.

There's no reason not to write the kernel, too, if you're writing your own OS--particularly, if it is an exokernel, which is will lend greater flexibility than monolithic kernels or microkernels. Yes, even greater flexibility to drivers (sure, you might still find yourself writing them). With an exokernel, one could utilize far greater things from other OSes--even have other OSes run on top of it. Some, quite unmodified. Depends on what one wishes to do.

I see no real reason in this article not to write a kernel, save for one based on experiences that might have simply created a personal bias against them. There will always be someone, somewhere, writing an OS kernel. The prospect and the interest is too great for some to avoid it.

I do, however, appreciate the one movement started by some of trying to implement a kernel for all. But, some like me would rather avoid even the general licenses of some things. Open source is here to stay, but it too is not ubiquitous.

--EyeAm (author of NOVIO)
http://s87767106.onlinehome.us/mes/NovioSite/index.html