Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Incompatible Timesharing System

From Wikipedia, the free encyclopedia
Operating system
Operating system
Incompatible Timesharing System (ITS)
Output from ITS PEEKtask manager on a simulatedCRT screen.
DeveloperMIT Artificial Intelligence Laboratory andProject MAC
Written inAssembly language
Working stateActive
Initial releaseJuly 1967; 58 years ago (1967-07)[1]
Repositorygithub.com/PDP-10/its
Available inEnglish
Supported platformsDigitalPDP-6,PDP-10, (emulators now available)
Default
user interface
Command-line interface (DDT)
LicenseGPL-3.0-or-later[2]

Incompatible Timesharing System (ITS) is atime-sharingoperating system developed principally by theMIT Artificial Intelligence Laboratory, with help fromProject MAC. The name is the jocular complement of the MITCompatible Time-Sharing System (CTSS).

ITS, and the software developed on it, were technically and culturally influential far beyond their core user community. Remote "guest" or "tourist" access was easily available via the earlyARPANET, allowing many interested parties to informally try out features of the operating system and application programs. The wide-open ITS philosophy and collaborativeonline community were a major influence on thehacker culture, as described in Steven Levy's bookHackers,[3] and were the direct forerunners of thefree and open-source software (FOSS),open-design, andWiki movements.

History

[edit]

ITS development was initiated in the late 1960s by those (the majority of the MIT AI Lab staff at that time) who disagreed with the direction taken by Project MAC'sMultics project (which had started in the mid-1960s), particularly such decisions as the inclusion of powerfulsystem security. The name was chosen byTom Knight as a joke on the name of the earliest MIT time-sharing operating system, theCompatible Time-Sharing System (CTSS), which dated from the early 1960s.[3]

By simplifying their system compared to Multics, ITS's authors[who?] were able to quickly[clarification needed] produce a functional operating system for their lab.[4] ITS was written inassembly language, originally for theDigital Equipment CorporationPDP-6 computer, but the majority of ITS development and use was on the newer, largelyupwards-compatible,PDP-10.[3]

Although not used as intensively after about 1986, ITS continued to operate on original hardware at MIT until 1990, and then until 1995 atStacken Computer Club [sv] in Sweden. Today, some ITS implementations continue to be remotely accessible, viaemulation of PDP-10 hardware running on modern, low-cost computers supported by interested hackers.

Significant technical features

[edit]

ITS introduced many then-new features:

  • The firstdevice-independentgraphics terminal output; programs generated generic commands to control screen content, which the system automatically translated into the appropriate character sequences for the particular type of terminal operated by the user.
  • A general mechanism for implementingvirtual devices in software running in user processes (which were called "jobs" in ITS).
  • Using the virtual-device mechanism, ITS provided transparentinter-machine filesystem access. The ITS machines were all connected to theARPAnet, and a user on one machine could perform the same operations with files on other ITS machines as if they were local files.
  • Sophisticatedprocess management; user processes were organized in atree, and a superior process could control a large number of inferior processes. Any inferior process could be frozen at any point in its operation, and its state (including contents of the registers) examined; the process could then be resumed transparently.
  • An advancedsoftware interrupt facility that allowed user processes to operate asynchronously, using complexinterrupt handling mechanisms.
  • PCLSRing, a mechanism providing what appeared (to user processes) to be quasi-atomic, safely-interruptiblesystem calls. No process could ever observe any process (including itself) in the middle of executing any system call.
  • In support of the AI Lab's robotics work, ITS also supported simultaneousreal-time and time-sharing operation.

User environment

[edit]

The environment seen by ITS users was philosophically significantly different from that provided by most operating systems at the time.[3]

  • Initially there were nopasswords, and a user could work on ITS without logging on.[5] Logging on was considered polite, though, so other people knew when one was active on the system.
  • To deal with a rash of incidents where users sought out flaws in the system in order tocrash it, a novel approach was taken. A command which could be run by anyone would cause the system to crash, taking away the challenge and notoriety of doing so. It first also broadcast a message to say who was initiating the crash.
  • All files were editable by all users, includingonline documentation andsource code. A series of informal papers and technical notes documented new commands, technical issues, primitive games, mathematical puzzles, and other topics of interest to the ITS hacker community. Some were issued as more formalAI Memos, including the iconicHAKMEM compendium.
  • All users could talk withinstant messaging on another's terminal, or they could use a command (SHOUT) to ask all active users for help.
  • Users couldsee what was happening on another's terminal (using a command called OS for "output spy"). A target of OS could detect and kill it using another command called JEDGAR, named afterFBI DirectorJ. Edgar Hoover. This facility was later disabled with aplacebo command: it appeared as if the remote session was killed, but it was not.[6]
  • Tourists (guest users either at MIT AI Lab terminals, or over the ARPAnet) were tolerated and occasionally invited to actively join the ITS community. Informal policy on tourist access was later formalized in a written policy.[7] Ease of access, with or without a guest account, allowed interested parties to informally explore and experiment with the operating system, application programs, andhacker culture. Working copies of documentation and source code could be freely consulted or updated by anybody on the system.
  • System security, to the extent that it existed, was mostly-based onde facto "security by obscurity". Guest hackers willing to dedicate significant time and effort to learning ITS were expected to behave respectfully, and to avoid interfering with the research projects which funded the hardware and software systems. There was little of exclusive value on the ITS systems except information, much of which would eventually be published for free distribution, and open and free sharing of knowledge was generally encouraged.

The wide-open ITS philosophy and collaborative community were the direct forerunner of thefree and open-source software (FOSS),open-design, andWiki movements.[8][9][10]

Important applications developed on ITS

[edit]

TheEMACS ("Editor MACroS") editor was originally written on ITS. In its ITS instantiation it was a collection ofTECO programs (called "macros"). On later operating systems, it was written in the common language of those systems – for example, theC language underUnix, andZetalisp under theLisp Machine system.

GNU′sinfo help system was originally an EMACS subsystem, and then was later written as a complete standalone system for Unix-like machines.

Several important programming languages and systems were developed on ITS, includingMacLisp (the precursor of Zetalisp andCommon Lisp),Microplanner (implemented in MacLisp),MDL (which became the basis ofInfocom's programming environment), andScheme.

Among other significant and influential software subsystems developed on ITS, theMacsyma symbolic algebra system, started in 1968, was the first widely-known mathematical computing environment. It was a forerunner ofMaxima,MATLAB,Wolfram Mathematica, and many othercomputer algebra systems.

Terry Winograd's natural-language interpreterSHRDLU was developed on ITS. The computer gameZork was also originally written on ITS.[citation needed]

Richard Greenblatt's Mac Hack VI was the top-rated chess program for years[citation needed] and was the first to display a graphical board representation.[citation needed]

Miscellaneous

[edit]

The default ITS top-levelcommand interpreter was the PDP-10 machine language debugger (DDT). The usualtext editor on ITS wasTECO and laterEmacs, which was written in TECO. Both DDT and TECO were implemented through simpledispatch tables on single-letter commands, and thus had no truesyntax. The ITStask manager was called PEEK.

The local spelling "TURIST" is an artifact of six-character filename (and other identifier) limitations, which is traceable to sixSIXBIT encoded characters fitting into a single 36-bit PDP-10 word. "TURIST" may also have been apun onAlan Turing, a pioneer of theoreticalcomputer science.[11] The less-complimentary term "LUSER" was also applied to guest users, especially those who repeatedly engaged in clueless or vandalous behavior.[12]

TheJargon File started as a combined effort between people on the ITS machines at MIT and at Stanford UniversitySAIL. The document described much of the terminology, puns, and culture of the two AI Labs and related research groups, and is the direct predecessor of theHacker's Dictionary (1983),[13] the first compendium of hacker jargon to be issued by a major publisher (MIT Press).

Different implementations of ITS supported an odd array of peripherals, including an automatic wire stripper devised by hacker Richard Greenblatt, who needed a supply of pre-stripped jumper wires of various lengths forwire-wrapping computer hardware he and others were prototyping. The device used astepper motor and a formerly hand-held wire stripper tool and cutter, operated bysolenoid, all under computer control from ITS software. The device was accessible by any ITS user, but was disappointingly unreliable in actual use.

TheXerox Graphics Printer (XGP), one of the first laser printers, was supported by ITS by 1974.[14] The MIT AI Lab had one of these prototype continuous roll-fed printers for experimentation and use by its staff. By 1982, the XGP was supplemented by aXerox Dover printer, an early sheet-fed laser printer.[15] Although any ITS user could send files to the laser printers, physical access to pick up printouts was limited to staff and others who obtained access to the MIT lab, to control usage of printer supplies which had to be specially ordered.

CTSS and ITS file systems have a number of design elements in common. Both have an M.F.D. (master file directory) and one or more U.F.D. (user file directories). Neither of them have nested directories (sub-directories) Both have file names consisting of two names which are a maximum of six-characters long. Both support linked files.

Original developers

[edit]

See also

[edit]

References

[edit]
  1. ^Project MAC Progress Report IV(PDF). 1967. p. 18. Archived fromthe original(PDF) on March 8, 2016.
  2. ^"README".MIT CSAIL. n.d. RetrievedNovember 10, 2022.
  3. ^abcdLevy, Steven (2010). "Winners and Losers".Hackers: Heroes of the Computer Revolution - 25th Anniversary Edition (1st ed.). Sebastopol, CA:O'Reilly Media. pp. 85–102.ISBN 978-1449388393.
  4. ^Stuart, Brian L. (2008).Principles of Operating Systems: Design & Applications. Cengage Learning EMEA. p. 23.ISBN 9781300668558.OCLC 221248143.
  5. ^Eastlake, Donald E. (1972). "ITS Status Report".MIT AI Laboratory Memos. AIM-238.hdl:1721.1/6194.
  6. ^Eric S. Raymond, ed. (December 29, 2003)."OS and JEDGAR".The Jargon File (4.4.7 ed.). RetrievedDecember 21, 2009.
  7. ^"MIT AI Lab Tourist Policy". January 15, 1997. RetrievedDecember 21, 2009.
  8. ^Pan, Guohua; Bonk, Curtis J. (April 2007)."A Socio-Cultural Perspective on the Free and Open Source Software Movement".International Journal of Instructional Technology & Distance Learning.4 (4). Archived fromthe original on 2014-10-12. Retrieved2014-06-02.
  9. ^Stallman, Richard M. (2002).Free Software, Free Society: Selected Essays of Richard M. Stallman. Lulu.com. p. 13.ISBN 9781882114986. Retrieved2014-06-02.
  10. ^"History of OSS".Software Development for the Masses. Retrieved2014-06-02.
  11. ^"turist".Dictionary.com. TuristDictionary.com, LLC. Retrieved2014-06-04.
  12. ^"luser".Dictionary.com. Dictionary.com, LLC. Retrieved2014-06-04.
  13. ^"The Original Hacker's Dictionary".dourish.com. Paul Dorish. Retrieved2014-06-16.
  14. ^"XGP Font Catalog"(PDF).MIT Dspace. Massachusetts Institute of Technology. May 24, 1974. Retrieved2021-08-20.
  15. ^Stacy, Christopher C. (7 September 1982)."Getting Started Computing at the Al Lab"(PDF).MIT Dspace. Massachusetts Institute of Technology. Retrieved2021-08-20.

Bibliography

[edit]

External links

[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Incompatible_Timesharing_System&oldid=1334538821"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp