Bibliography of Single Address Space OSs and Related Articles
Part of Computer Science Bibliography Collection of Alf-Christian Achilles. |
Grasshopper
Orthogonally persistent, research SASOS. Persistence gives a fundamentally different model of computing from that supported by normal OSs, so using them for persistence research is inappropriate. |
Grasshopper OS: The Grand Unified Theory of Address Spaces
One of the reports available on a list of publications from Grasshopper OS. Scroll down to mid-page. |
Mungi
Orthogonally persistent, capability-based secure SASOS built on L4 2nd generation microkernel. Goals: Prove SASOSs can run on normal hardware, be as secure as normal OSs, are not inherently less efficient than normal OSs, are faster than normal OSs for s |
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. |
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. |
SASOS and Sombrero Project
SASOS research, and the Sombrero OS, at Arizona State University. |
Single Address Space Operating Systems
Short, annotated, alphabetically sorted list and links, part of larger system. |
Single Address Space Operating Systems Archive, Dartmouth
Mail lists, projects, biographies (BibTeX, HTML long, HTML sans abstracts), a few links to other SASOS sites. |
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 extensive kernel-level tracing of department workstations. |
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 u |
Vapour
OS based on single address space, persistent store: no kernel, processes, filesystem. Allows varied multitasking systems, including preemptive; and multiple users. Security via preventing interface violation, includes undefined behavior; language level s |
