This project intends to develop an exokernel based OS incorporating concepts from the MIT exokernel, the Utah Flux Project Elysium and Eros. The resulting system will also be a platform for emulating linux and a platform for developing a 3d user interface
Be the first to post a text review of The Quarq Subnucleus Project. Rate and review a project by clicking thumbs up or thumbs down in the right column.
since llvm is not ready yet, i have moved on to using gcc. i am testing the core. the environment handling and scheduling is being developed now. I am studying Earliest Eligible Virtual Deadline first algorithm which is similar to the current CFS in linux. I am planning to release the event core containing only interrupt stubs, environment and scheduler. The rest will be in environment and a libOS which is most likely plan9 like. But anything can happen. I might eventually end up reinventing linux in user space.
Im moving the entire development toolchain to llvm. This is going to be used to build kernel and user space.
Bye bye gnu make! bye bye autotools! the new build system can now build itself. The makefile fragments are written in c and it is proprocessed into a c file and compiled into an executable that is then executed to do the actual build. It is inspired by icmake and logilogi.org make.
I have restarted developement of the kernel after resolving the directed yield handling in the mit exokernel. This particular issued stymied me when i first tried to reimplement the exokernel. I am doing test driven development this time so i can test the code in userspace as much as possible. Only the absolute minimum will be written in assembly. The coding style is very radical. Im not using macros at all. No conditional compilation and i use #import exclusively. The Makefiles are all non recursive and im reimplementing make at the same time.
The gnustep based environment development is already started. Testing is being done to determine the best filesystem heirarchy which will most probably be based on nextstep.
i have restarted development of subnucleus. im reimplementing parts of the oskit tree to be able to build the lowest layers of the kernel. interrupt handling and cpu multiplexing and execution of userspace programs. no system calls. just but up initialize the cpu and userspace and run a predefined number of environments.
i have restarted development of subnucleus. im reimplementing parts of the oskit tree to be able to build the lowest layers of the kernel. interrupt handling and cpu multiplexing and execution of userspace programs. no system calls. just but up initialize the cpu and userspace and run a predefined number of environments.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?
Thanks for your review!
Get credit for your review by logging in via OpenID. Click your account provider: