Codezero:
http://www.l4dev.org/doku.php
This next OS needs another layer on top of the UI technology that directly talks to the user. I think that to directly integrate the user into the system, there has to be some kind of mind-mapping interaction with the OS as part of the capabilities that are offered to the user in the UI. Beyond this, the user needs to integrate into the "cloud," which is the rest of society, through the mind mapping, which then becomes minds-mapping. (??)
There is a need for the user to break out of the "client / server" mode, where I see the server as master and the client as slave, a direct extension of the original Information Society that the Jews escaped from: "Let my people go!!" This necessitates one to one connections between devices of this model where the connections are only supported by services but not controlled by them (presumably for money, or "tribute").
Equally important is full support for hardware manufacturers especially with respect to plug-in modules: completing the break from monolithic architecture. Completing this break is what l4 is about. Possibly even going further, a facility could be created to easily convert existing drivers to show manufacturers "good faith" respect to the peripheral market.
In my opinion, the most "excellent" architecture belongs to the "Parrot VM," which unfortunately has stalled, and perhaps needs to fork away from its parentage in Perl towards internal support. In short its programming language resembles CPU architecture in that it does uses registers making it factors more efficient, which of course lends to miniaturization and low power use.
LISP persists as a well-perfected interpreter language, and might make a model for the next system's native management language, though I would use names like "mash-up" or "zing" to describe a language and try to base it on the most accepted and popular interpretations of OO architecture.
I feel if all the necessary architectural aspects of an essential OS are represented, expert voices can implement their architectural ideas so as to finally give the world what it really needs.
Paraphrasing Bahadir Balban:
Codezero is a modern L4 microkernel implementation written in C that targets embedded platforms and aims to implement native OS components. It has a design and API that is similar to existing L4 microkernels.
Two current services: a default pager called MM0 that supports for instance fork, clone, execve, exit, mmap, shm. The second called FS0 and implements the virtual filesystem layer supporting open, close, read, write, lseek, stat, fsync, etc.
It is GPLv3 licensee, and a copyright share agreement option for contributions. On the next few releases there will be a port of the Xynth windowing system. Only that ARM is supported as the first architecture.
No comments:
Post a Comment