Linked by Julien Quintard on Tue 27th Jun 2006 17:33 UTC
OSNews, Generic OSes This paper describes the design of the kaneton microkernel. This system was designed to be ported on many architectures without being intrusive. Moreover, the main goal of this system was to be understandable by everyone interested in operating systems internals. To do so, the kaneton design and implementation are very elegant and easy to understand. Finally, the kaneton microkernel includes modern distributed concepts leading to a powerful, secure, flexible and reliable microkernel based OS. Note: This is the first entry to our Alternative OS Contest which runs through 14th July!
Thread beginning with comment 137774
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Hate to shoot someone down...
by Adam S on Tue 27th Jun 2006 20:27 UTC in reply to "Hate to shoot someone down..."
Adam S
Member since:
2005-04-01

This entry is not elligible to win unless they produce either the source OR an available binary (it can even be commercial). It simply has to be available in some way, shape, or form to qualify.

Reply Parent Bookmark Score: 1

JulienQuintard Member since:
2006-06-27

I can add something to the kaneton website like "source code for sale: 3 billion dollars"...

More seriously we are not doing this contest to win. just to share our ideas.

Reply Parent Bookmark Score: 3

wacco Member since:
2006-06-27

Sharing ideas is always good! In that case only kudos to writing a 7 page article without intention of actually participating in the actual 'contest'. On those terms, I feel obliged to give some more constructive feedback to it.

For starters, the following two quotes are very contradictive;
"leading to a powerful *snip* microkernel based OS"
"the microkernel translates every event into a message"
Ouch! Microkernels' *main* (and when going exo~ it's basically it's *only*) task is doing the IPC. And you guys give that even more overhead? It really gets me thinking about the performance of this OS. How did you tackle this?

Second; Your discussion about the set-manager rings a bell. How much is your OS based on L4? If I recall correctly, they have a similar concept.

Third; A basic idea of a microkernel is 'if something goes down, reboot just that'. How do you deal with such situations? This is even more relevant (and interesting) when you take the network-distributed part in mind. Some info about that would be really nice. ;)

Lastly; the main objective was to build an educational OS. But the article discusses things like network-distributed file-descriptor encryption. Besides the obvious 'what algorithm and how easy will it be to crack', isn't that a little far-fetched for an educational OS?

Reply Parent Bookmark Score: 1