From: Kasper V. L. <ve...@da...> - 2000-03-14 07:30:52
|
> Why the merge? IMHO we need the few -- but good/active -- developers from the Apostle project. > So how will the micro-kernel be like? Will it have a lower level interface than > say mach or fluke? Much lower -- nothing like Mach or Fluke. > How exo-ish is it going to be? It's the current Elysium design. The current design is a 'micro-kernel *based* exokernel' -- traditional micro-kernel aims for providing (and enforcing) the best/right abstractions - we don't enforce any (at least not any that aren't strictly necessary for protection). > I would rather stick to pure exo-principles. Im an exo nut. We will stick to pure exo-principles. The design of the 'new' kernel is based on 100% pure exo-principles. I'm an exo-nut as well -- and I'm sorry for not making that 100% clear in the previous posting. Let me make this clear once and for all: The Elysium *kernel* will change name and become a separate project on SourceForge. The design principles will *not* change, and most of the code already written will be imported into the new project without modifications. In fact the most important change will probably be that we'll be using 'autoconf' and 'automake' for the makefiles, and that we'll have a few more developers :-). > As for the code Im taking out my old exokernel code and revive it. I cant > continue on developing the Elysium right? Of course you can :-) You just have to use cvs -d<something>@cvs.<somethingelse>.sourceforge.net co kernel instead of cvs -d<something>@cvs.elysium.sourceforge.net co kernel I'll keep you posted. /Kasper -- ------------------------------------------------------------------- Kasper Verdich Lund, Computer Science Department, Aarhus University Office: 34P.218 | Phone: (+45) 8942 5680 Email: ve...@da... | WWW: http://www.daimi.au.dk/~verdich |