Difference between revisions of "Berkeley Time-Sharing System"
m (→External links: +A User Machine in a Time-Sharing System) |
m (Name per original docs) |
||
| Line 1: | Line 1: | ||
| − | The '''Berkeley | + | The '''Berkeley Time-Sharing System''' was a very influential [[time-sharing]] [[operating system]] for an enhanced [[Scientific Data Systems|SDS]] [[SDS 930|930]] (effectively the prototype of the later [[SDS 940]]). |
It was produced by [[Project GENIE]] at Berkeley; it was primarily written by L. Peter Deutsch, [[Butler Lampson]], and Chuck Thacker. It was later updated by Ann Hardy at [[Tymshare]] and named TYMCOM; later [[TYMCOM-IX]]. | It was produced by [[Project GENIE]] at Berkeley; it was primarily written by L. Peter Deutsch, [[Butler Lampson]], and Chuck Thacker. It was later updated by Ann Hardy at [[Tymshare]] and named TYMCOM; later [[TYMCOM-IX]]. | ||
Revision as of 21:53, 10 June 2023
The Berkeley Time-Sharing System was a very influential time-sharing operating system for an enhanced SDS 930 (effectively the prototype of the later SDS 940).
It was produced by Project GENIE at Berkeley; it was primarily written by L. Peter Deutsch, Butler Lampson, and Chuck Thacker. It was later updated by Ann Hardy at Tymshare and named TYMCOM; later TYMCOM-IX.
It had a substantial influence on the early design of UNIX; Ken Thompson had worked on it while he was at Berkeley, and was very familiar with it, and some aspects of Unix (e.g. the split between fork() and exec()) copy how the Berkeley system operated. It was also one of the influences on TENEX.
The kernel was named the 'Monitor', and the command processor the 'Executive'. Application software included an interpretive programming language called 'CAL', inspired by, and very similar to, JOSS.
Supposedly, it featured a limited version of PCLSRing. From Mark Emmer:
- From what I read of the PCLSRing feature, it would be the equivalent of SYSPOPs (System Programmed Operators) in the 940 system. That is, system calls appeared to be atomic while also being interruptible. During an interrupt, the PC would point to the original SYSPOP, perhaps with altered registers for things like counts and memory pointers, reflecting incremental progress with the system call. The user PC would never point to an address within the monitor. On interrupt return, the SYSPOP would be restarted in user space.
External links
- Project Genie - documentation at Bitsavers
- B. W. Lampson, M. W. Pirtle, W. W. Lichtenberger, A User Machine in a Time-Sharing System
