|
| | Bibliography of Single Address Space OSs and Related Articles     |
| | Part of Computer Science Bibliography Collection of Alf-Christian Achilles.
http://liinwww.ira.uka.de/bibliography/Os/sasos.html |
|
|
| | The Expected Lifetime of Single Address Space Operating Systems |
| | Where stale pointers make it hard to re-use addresses, some have claimed that a 64-bit address space is so big that there is no need to ever re-use addresses. Results of kernel-level tracing of department workstations. [PDF]
http://www.cs.dartmouth.edu/~dfk/papers/kotz:addrtrace.pdf |
|
|
| | Mungi |
| | Orthogonally persistent, capability-based secure SASOS using L4 2nd generation microkernel. Goals: Prove SASOSs can run on normal hardware, be as secure as normal OSs; can be as efficient as, and are faster than, normal OSs in some important uses; can be pure SASOSs with all data (even system data) in one address space and no other IPC mechanism is supported by OS. POSIX emulating. [Open Source, GPL]
http://www.cse.unsw.edu.au/~disy/Mungi/ |
|
|
| | Opal |
| | Exploring a new OS structure, tuned to the needs of complex applications (eg, CAD/CAM) where a number of cooperating programs manipulate a large shared persistent database of objects.
http://www.cs.washington.edu/homes/levy/opal/opal.html |
|
|
| | ResearchIndex: Architectural Support for Single Address Space Operating Systems |
| | From Proceedings of the International Conference on Architectural Support for Programming Languages and Operating Systems, Boston, USA, October 1992.
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.16.9704 |
|
|
| | SASOS and Sombrero Project |
| | SASOS research, and the Sombrero OS, at Arizona State University.
http://www.eas.asu.edu/~sasos/ |
|
|
| | Single Address Space Operating Systems Archive, Dartmouth |
| | Mail lists, projects, biographies (BibTeX, HTML long, HTML sans abstracts), a few links to other SASOS sites.
http://www.cs.dartmouth.edu/~dfk/sasos/ |
|
|
| | Torsion |
| | Multitasking SASOS with transparent data persistence: users and application programmers need not know or care that system memory is transient and must be written to disk to persist across reboots, all details done by OS, so once data is made, it exists until explicitly destroyed, like physical objects. [Open Source, GPL]
http://www.torsion.org/ |
|
