- Opal - http://www.cs.washington.edu/homes/levy/opal/opal.html
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.
- Mungi - http://www.cse.unsw.edu.au/~disy/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]
- The Expected Lifetime of Single Address Space Operating Systems - http://www.cs.dartmouth.edu/~dfk/papers/kotz:addrtrace.pdf
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 - http://www.torsion.org/
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]
- Grasshopper - http://os.dcs.st-and.ac.uk/GH/Grasshopper.html
Orthogonally persistent, research SASOS. Persistence gives a fundamentally different model of computing from that supported by normal OSs, so using such for persistence research is inappropriate.
- The Grand Unified Theory of Address Spaces - http://os.dcs.st-and.ac.uk/GH/Papers/Papers.html
One of many reports available on a list of publications from Grasshopper OS. Scroll down to mid-page. Explains rationale and design approach for SASOSs. Abstracts, FTP downloads in formats: PDF, PS, PS.GZ.
|
