Compatible Time-Sharing System

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Compatible Time-Sharing System
Developer MIT's Computation Center
Working state Historic
Initial release 1961
Marketing target MIT only
Available in English
Platforms modified IBM 7094
Official website {{#property:P856}}

The Compatible Time-Sharing System (CTSS), was one of the first time-sharing operating systems; it was developed at MIT's Computation Center. CTSS was first demonstrated in 1961, and was operated at MIT until 1973. During part of this time, MIT's influential Project MAC also ran CTSS, but the system did not spread beyond these two sites.

CTSS was described in a paper presented at the 1962 Spring Joint Computer Conference, and greatly influenced the design of other early time-sharing systems.

Lua error in package.lua at line 80: module 'strict' not found.

Overview

The "Compatible" in the name refers to backwards compatibility with the standard batch processing OS for the IBM 7094, the FORTRAN Monitor System (FMS). CTSS ran an unaltered copy of FMS, processing a standard batch stream, in a pseudo-virtual 7094 provided by its background facility. (The hardware was partly but not fully virtualized; see History of CP/CMS for further details.) Background FMS jobs could access tapes normally, but could not interfere with foreground time-sharing processes or the resources used to support them.

CTSS was very influential. It showed that time-sharing was viable; it fostered important new applications for computers; it had a significant influence on the next generation of time-sharing systems, notably CP/CMS. Its direct successor, Multics, pioneered many core concepts of current operating systems.

Characteristics

  • CTSS had one of the first computerized text formatting utilities, called RUNOFF.
  • CTSS had one of the first inter-user messaging implementations, possibly inventing email.[1]
  • MIT Computation Center staff member Louis Pouzin created for CTSS a command called RUNCOM, which executed a list of commands contained in a file. (He later created a design for the Multics shell, which in turn inspired Unix shell scripts.) RUNCOM also allowed parameter substitution.

Implementation

CTSS used a modified IBM 7094 mainframe computer that had two 32,768 (32K) 36-bit-word banks of core memory instead of the normal one; users had access to 27K of the total 32K words, with the remaining 5K words reserved for the monitor.[2] One bank was reserved for the time-sharing supervisory program, the other for user programs. Processor allocation scheduling was controlled by a multilevel feedback queue.[2] It also had some special memory management hardware, a clock interrupt and the ability to trap certain instructions. Input-output hardware was mostly standard IBM peripherals. These included six data channels connecting to:

  • Printers, punched card readers and punches
  • IBM 729 tape drives, an IBM 1301 disk storage, later upgraded to an IBM 1302, with 38 million word capacity
  • An IBM 7320 drum memory with 186K words that could load a 32K-word memory bank in one second (later upgraded to 0.25 seconds)
  • Two custom high speed vector graphics displays
  • An IBM 7750 transmission control unit capable of supporting up to 112 teleprinter terminals, including IBM 1050 Selectrics and Teletype Model 35s. Some of the terminals were located remotely and the system could be accessed using the public Telex and TWX networks.

Influences

Multics, which was also developed by Project MAC, was started in the 1960s as a successor to CTSS – and in turn inspired the development of Unix in 1969. One of technical terms inherited by these systems from CTSS is daemon.

ITS, the Incompatible Timesharing System, another early, revolutionary, and influential MIT time-sharing system, was produced by people who disagreed with the direction taken by CTSS and later, Multics; the name was a parody of CTSS, as later the name of Unix was a parody of Multics.[3]

See also

References

  1. Tom Van Vleck's memoir of The History of Electronic Mail
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.

External links