From: Kasper V. L. <ve...@da...> - 2000-03-13 13:23:25
|
Dear fellow developers, In a matter of days the Elysium Project is going to merge with the Apostle Project. Please read the attachment following my signature. If you have any questions/doubts regarding the merge please let me -- or at your option the entire mailing list -- know. The plan is to combine our efforts to produce a GNU GPL'ed micro-kernel (built on exokernel principles and the current Elysium design) suitable for a wide variety of applications. As stated in the attachment the development on the Elysium kernel will cease, but I expect to continue the Elysium Project -- just for the sake of the name. The goal of the 'new' Elysium Project will be to create an operating system environment based on the GNU GPL'ed micro-kernel. We need a good name for the micro-kernel -- any good suggestions? /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 ----- Original Message ----- From: "Guido de Jong" <gu...@dd...> To: "Apostle Developers" <apo...@li...> Sent: Sunday, March 12, 2000 11:11 PM Subject: [apostle-developers] Apostle + Elysium = ? > Hi all! > > As you might know, Kasper (Apostle Project administrator "verdich"), is > also working on another OS project called Elysium. This weekend Kasper > and I (being the two most active developers of Apostle and Elysium) got > together digitally to discuss merging Apostle and Elysium. We agreed > that in stead of building two competing systems it would be better to > combine our efforts. It means that we will have a working system a lot > faster, for which - correct me if I'm wrong - most of you are really > waiting. > > We intend to create a whole new project on SourceForge for the kernel > development. Later on we will create another project containing > libraries/drivers and such. This also means that the development for > Apostle (and Elysium) will stop once we have our new project going. All > current developers are encouraged to join our new project. > > At this point, the biggest problem we are facing is a name for the new > kernel project. We thought that you might actually have some good ideas > for a name. So please feel free to make any suggestions! > > Guido > > _______________________________________________ > apostle-developers mailing list > apo...@li... > http://lists.sourceforge.net/mailman/listinfo/apostle-developers > |
From: Rogelio M. S. Jr. <ro...@ev...> - 2000-03-13 23:14:10
|
Kasper Verdich Lund wrote: > Dear fellow developers, > > In a matter of days the Elysium Project is going to merge with the Apostle > Project. Please read the attachment following my signature. If you have any > questions/doubts regarding the merge please let me -- or at your option the > entire mailing list -- know. > > The plan is to combine our efforts to produce a GNU GPL'ed micro-kernel > (built on exokernel principles and the current Elysium design) suitable for > a wide variety of applications. As stated in the attachment the development > on the Elysium kernel will cease, but I expect to continue the Elysium > Project -- just for the sake of the name. The goal of the 'new' Elysium > Project will be to create an operating system environment based on the GNU > GPL'ed micro-kernel. > > We need a good name for the micro-kernel -- any good suggestions? > > /Kasper Why the merge? So how will the micro-kernel be like? Will it have a lower level inerface than say mach or fluke? How exo-ish is it going to be? I would rather stick to pure exo-principles. Im an exo nut. As for the code Im taking out my old exokernel code and revive it. I cant continue on developing the Elysium right? |
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 |
From: Rogelio M. S. Jr. <ro...@ev...> - 2000-03-14 09:17:33
|
ok im joining i'll try to be more active this time Kasper Verdich Lund wrote: > > 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 > > _______________________________________________ > elysium-developers mailing list > ely...@li... > http://lists.sourceforge.net/mailman/listinfo/elysium-developers -- ----------------------------------------------------- Click here for Free Video!! http://www.gohip.com/freevideo/ |