Difference between revisions of "Berkeley Time-Sharing System"
From Computer History Wiki
(Link to Lampson.) |
(their 930 was the progenitor of the later 940) |
||
| Line 1: | Line 1: | ||
| − | The '''Berkeley Timesharing System''' was a [[time-sharing]] [[operating system]] for an enhanced [[Scientific Data Systems|SDS]] [[SDS 930|930]]. Primarily written by L. Peter Deutsch, [[Butler Lampson]], and Chuck Thacker. | + | The '''Berkeley Timesharing System''' was a [[time-sharing]] [[operating system]] for an enhanced [[Scientific Data Systems|SDS]] [[SDS 930|930]] (effectively the prototype of the later [[SDS 940]]). Primarily written by L. Peter Deutsch, [[Butler Lampson]], and Chuck Thacker. |
It had an influence on the early design of [[UNIX]]; Ken Thompson 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 had an influence on the early design of [[UNIX]]; Ken Thompson was very familiar with it, and some aspects of Unix (e.g. the split between ''fork()'' and ''exec()'') copy how the Berkeley system operated. | ||
| Line 5: | Line 5: | ||
It was also one of the influences on [[TENEX]]. | It was also one of the influences on [[TENEX]]. | ||
| − | Supposedly, it featured a limited version of PCLSRing. | + | 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.'' | : ''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.'' | ||
Revision as of 23:51, 3 May 2022
The Berkeley Timesharing System was a time-sharing operating system for an enhanced SDS 930 (effectively the prototype of the later SDS 940). Primarily written by L. Peter Deutsch, Butler Lampson, and Chuck Thacker.
It had an influence on the early design of UNIX; Ken Thompson 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.
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.
