Marcus Brinkmann wrote: > So you see, it is not about L4, but about glueing Hurd to L4. Mach did a > lot of things for us that L4 is not doing, and we take the chance to try to > more consequently implement the Hurd's fundamental design ideas. Freedom to > the users! Freedom to map your physical memory as you want it, freedom to > use the IPC policy you want, and the freedom to have functional device > drivers without getting them approved by a kernel master geek ;)
L4 also provides for user-space scheduling, besides the standard in-kernel scheduler. Putting the scheduling policy out of the kernel opens up new interesting possibilities, like, perhaps real-time threads and better support for SMP systems as well. As Marcus said, it's all about freedom. And it's fun too! -- Farid Hajji. http://www.farid-hajji.net/address.html