Currently, operating systems are not chosen for underlying system features, but rather for the performance of the underlying hardware, available application programs, and system stability. Consequently, operating system vendors are reluctant to incorporate new operating system functionality since they risk both increased development time and decreased system stability. Previous efforts to make it easier for operating systems to incorporate new features have enjoyed only limited success because of performance bottlenecks or limited support for existing applications. This paper outlines a portable, efficient, and robust method for extending operating system functionality. Specifically, we propose building operating systems entirely as a library linked with every application using software-based fault isolation for protection. In order to demonstrate the validity of this technique, we are building an operating system which will provide global resource allocation in a network of workstations.
Title
Efficient, Portable, and Robust Extension of Operating System Functionality
Published
Computer Science Division, University of California at Berkeley, Berkeley, California, December 5, 1994
Full Collection Name
Electrical Engineering & Computer Sciences Technical Reports
Other Identifiers
CSD-94-842
Type
Text
Extent
5 p
Archive
The Engineering Library
Usage Statement
Researchers may make free and open use of the UC Berkeley Library’s digitized public domain materials. However, some materials in our online collections may be protected by U.S. copyright law (Title 17, U.S.C.). Use or reproduction of materials protected by copyright beyond that allowed by fair use (Title 17, U.S.C. § 107) requires permission from the copyright owners. The use or reproduction of some materials may also be restricted by terms of University of California gift or purchase agreements, privacy and publicity rights, or trademark law. Responsibility for determining rights status and permissibility of any use or reproduction rests exclusively with the researcher. To learn more or make inquiries, please see our permissions policies (https://www.lib.berkeley.edu/about/permissions-policies).
