What Are Object-Oriented Operating Systems?
Refs to be included in future FAQs. See also Appendix E. Object-Oriented Operating Systems provide resources through objects, sometimes all the way down to to the machine (OO architectures are found at the bottom). They are almost always distributed systems (DOS or DPOS), allowing objects to be passed freely between machines. They are typically capability-based since objects, and hence system resources, can only be accessed if a capability to them is available to programs. Here are some abstracts taken from several postings to the net. This list is by no means exhaustive. • Apertos (Meta-Object-based Mikro-Kernel. See Appendix E, Papers:28) • Chorus Micro-kernel (written in C++, COOL, See Appendix E, Papers:63) • Choices (research OS, UofI, C++, supports SVR4, See Appendix E, Papers) • GEOS (GeoWorks’, written in Object Assembler, OO superset of 8086) • Mach (CMU, supports BSD 4.3, really message-based) • NachOS (written in C++, OS teaching/learning OS) • Ouverture Project (ESPRIT fund
