05-04-2010, 09:05 PM
Abstract
This paper describes Grasshopper, an operating system designed to provide generic mechanisms capable of being tailored to support a wide range of persistence paradigms. A constraint placed on this design is that the system must be implementable on conventional architectures which support paged virtual memory. In this paper the basic system abstractions relating to addressing environments, processes, and protection are described. It is shown that these provide explicit support for distributed persistent objects and processes, stability, and access control. At the same time the system provides the flexibility to allow user implementation of alternate object management techniques.
Presented By:
 Alan Dearle, *Rex di Bona, *James Farrow, *Frans Henskens,
*Anders Lindström, *John Rosenberg,  Francis Vaughan
1. Introduction
Most persistent systems developed to date have been constructed above conventional operating systems. The fact that these operating systems do not provide an ideal platform for such construction is not surprising since support for the principles of orthogonal persistence was not among their design goals. In [21], for example, Tanenbaum lists the four major components of an operating system as being memory management, file system, input-output and process management. persistent systems the functionality of the file system and memory management is replaced by the persistent store. Many conventional operating systems extend the file abstraction to encompass input and output, an approach which is obviously inappropriate for persistent systems. Some persistent systems require that the state of a process persists. This is not easily supported using conventional operating systems.
read full report
http://cs.newcastle.edu.au/~henskens/papers/IWOOS92.pdf
http://citeseerx.ist.psu.edu/viewdoc/dow...1&type=pdf
http://ieeexplore.ieeeiel2/439/6454/0025...ber=252996
