Protection in Grasshopper: A Persistent Operating System

Alan Dearle; R di Bona; J Farrow; F Henskens; D Hulse; A Lindström; S Norris; J Rosenberg; F Vaughan

Protection in Grasshopper: A Persistent Operating System

Alan Dearle, R di Bona, J Farrow, F Henskens, D Hulse, A Lindström, S Norris, J Rosenberg, F Vaughan

School of Computer Science

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution

Abstract

Persistent systems support a single storage abstraction in which all data may be created and manipulated in a uniform manner, regardless of its longevity. In such systems a protection mechanism is required to ensure that programs can access precisely those objects they are supposed to access and no others. In a monolingual system this protection can be provided by the type system of the programming language; in systems which support multiple persistent languages a separate protection mechanism must be supported. This paper describes the capability-based protection mechanism employed in Grasshopper, a new operating system specifically designed to support persistent systems on a conventional workstation platform. We show that this mechanism provides sufficient power and flexibility to handle a wide variety of protection scenarios.

Original language	English
Title of host publication	Persistent Object Systems; Proc 6th International Workshop on Persistent Object Systems (POS6)
Place of Publication	Tarascon, France
Pages	60-78
Publication status	Published - 1994

Handle.net

Persistent link

Cite this

@inproceedings{35ddbf82f4f14c7cb042aaf09f039566,

title = "Protection in Grasshopper: A Persistent Operating System",

abstract = "Persistent systems support a single storage abstraction in which all data may be created and manipulated in a uniform manner, regardless of its longevity. In such systems a protection mechanism is required to ensure that programs can access precisely those objects they are supposed to access and no others. In a monolingual system this protection can be provided by the type system of the programming language; in systems which support multiple persistent languages a separate protection mechanism must be supported. This paper describes the capability-based protection mechanism employed in Grasshopper, a new operating system specifically designed to support persistent systems on a conventional workstation platform. We show that this mechanism provides sufficient power and flexibility to handle a wide variety of protection scenarios.",

author = "Alan Dearle and \{di Bona\}, R and J Farrow and F Henskens and D Hulse and A Lindstr{\"o}m and S Norris and J Rosenberg and F Vaughan",

year = "1994",

language = "English",

isbn = "3-540-19912-8",

pages = "60--78",

booktitle = "Persistent Object Systems; Proc 6th International Workshop on Persistent Object Systems (POS6)",

}

TY - GEN

T1 - Protection in Grasshopper: A Persistent Operating System

AU - Dearle, Alan

AU - di Bona, R

AU - Farrow, J

AU - Henskens, F

AU - Hulse, D

AU - Lindström, A

AU - Norris, S

AU - Rosenberg, J

AU - Vaughan, F

PY - 1994

Y1 - 1994

N2 - Persistent systems support a single storage abstraction in which all data may be created and manipulated in a uniform manner, regardless of its longevity. In such systems a protection mechanism is required to ensure that programs can access precisely those objects they are supposed to access and no others. In a monolingual system this protection can be provided by the type system of the programming language; in systems which support multiple persistent languages a separate protection mechanism must be supported. This paper describes the capability-based protection mechanism employed in Grasshopper, a new operating system specifically designed to support persistent systems on a conventional workstation platform. We show that this mechanism provides sufficient power and flexibility to handle a wide variety of protection scenarios.

AB - Persistent systems support a single storage abstraction in which all data may be created and manipulated in a uniform manner, regardless of its longevity. In such systems a protection mechanism is required to ensure that programs can access precisely those objects they are supposed to access and no others. In a monolingual system this protection can be provided by the type system of the programming language; in systems which support multiple persistent languages a separate protection mechanism must be supported. This paper describes the capability-based protection mechanism employed in Grasshopper, a new operating system specifically designed to support persistent systems on a conventional workstation platform. We show that this mechanism provides sufficient power and flexibility to handle a wide variety of protection scenarios.

UR - https://archive.cs.st-andrews.ac.uk/papers/download/DdF+94a.pdf

M3 - Conference contribution

SN - 3-540-19912-8

SP - 60

EP - 78

BT - Persistent Object Systems; Proc 6th International Workshop on Persistent Object Systems (POS6)

CY - Tarascon, France

ER -

Protection in Grasshopper: A Persistent Operating System

Abstract

Handle.net

Other files and links

Fingerprint

Cite this