TENEX (operating system)

<h2 id="background">Background</h2>
<p>In the 1960s, <a href="/facts/BBN_Technologies/9kA7axL3">BBN</a> was involved in a number of <a href="/facts/LISP/xJHA3CrX">LISP</a>-based <a href="/facts/Artificial_intelligence/lJGauQwX">artificial intelligence</a> projects for <a href="/facts/DARPA/Uf9sarhT">DARPA</a>, many of which had very large (for the era) memory requirements. One solution to this problem was to add <i><a href="/facts/Paging/KR889x5k">paging</a></i> software to the <a href="/facts/LISP/xJHA3CrX">LISP</a> language, allowing it to write out unused portions of memory to disk for later recall if needed. One such system had been developed for the <a href="/facts/PDP-1/PSeIBDJU">PDP-1</a> at <a href="/facts/MIT/Xk49vNA8">MIT</a> by <a href="/facts/Daniel_Murphy_(computer_scientist)/wKz6xReT">Daniel Murphy</a> before he joined BBN. Early <a href="/facts/Digital_Equipment_Corporation/ztxs6keA">DEC</a> machines were based on an <a href="/facts/18-bit_computing/CgrYUIxM">18-bit</a> word, allowing addresses to encode for a 256 <a href="/facts/Kiloword/2e5umRaj">kiloword</a> memory. The machines were based on expensive <a href="/facts/Magnetic-core_memory/4TFIXSNd">core memory</a> and included nowhere near the required amount.  The pager used the most significant bits of the address to index a table of blocks on a <a href="/facts/Magnetic_drum/yul0r8nG">magnetic drum</a> that acted as the pager's <i>backing store</i>.  The software would fetch the pages if needed, and then resolve the address to the proper area of <a href="/facts/RAM/DuD4bxh6">RAM</a>.
</p><p>In 1964 DEC announced the <a href="/facts/PDP-6/dlvBVlr8">PDP-6</a>. DEC was still heavily involved with MIT's AI Lab, and many feature requests from the LISP hackers were moved into this machine. 36-bit computing was especially useful for LISP programming because with an 18-bit address space, a word of storage on these systems contained two addresses, a perfect match for the common LISP <a href="/facts/CAR_and_CDR/cC7hhymV">CAR and CDR</a> operations. BBN became interested in buying one for their AI work when they became available, but wanted DEC to add a hardware version of Murphy's pager directly into the system. With such an addition, every program on the system would have paging support invisibly, making programming much easier. DEC was initially interested, however in 1966 they announced they would be discontinuing the PDP-6 and concentrating solely on their smaller 18-bit and new 16-bit lines. The PDP-6 was expensive and complex, and therefore had not sold well.
</p><p>It was not long until it became clear that DEC was once again entering the <a href="/facts/36-bit_computing/P0V83YtM">36-bit</a> business with what would become the <a href="/facts/PDP-10/zlfam4wk">PDP-10</a>. BBN started talks with DEC to get a paging subsystem in the new machine, then known by its CPU name, the KA-10. DEC was not interested; however, one development of these talks was support in the PDP-10 for a second virtual memory segment, allowing half of the user address space to be mapped to a separate (potentially read-only) region of physical memory. Additionally, DEC insisted on keeping the cost of the machine as low as possible, such as supporting systems with a minimum of 16K words of core, and omitting the fast semiconductor <a href="/facts/Processor_register/32RvbUdz">register</a> option (substituting core), at the cost of a considerable performance decrease.
</p>
<h2 id="bbn-and-pdp-10s">BBN and PDP-10s</h2>

<p>BBN nevertheless went ahead with its purchase of several PDP-10s, and decided to build their own hardware pager.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> During this period a debate began on what operating system to run on the new machines. Strong arguments were made for the continued use of TOPS-10, in order to keep their existing software running with minimum effort. This would require a re-write of TOPS-10 to support the paging system, and this seemed like a major problem. At the same time, TOPS-10 did not support a number of features the developers wanted. In the end they decided to make a new system, but include an emulation library that would allow it to run existing TOPS-10 software with minor effort.
</p><p>The developer team—amongst them <a href="/facts/Daniel_Murphy_(computer_scientist)/wKz6xReT">Daniel Murphy</a> and <a href="/facts/Daniel_G._Bobrow/GKssbwds">Daniel G. Bobrow</a>—chose the name TENEX (TEN-EXtended) for the new system. It included a full <a href="/facts/Virtual_memory/Lw2GemF5">virtual memory</a> system—that is, not only could programs access a full 18 bit address space of 262144 words of virtual memory, <i>every</i> program could do so at the same time. The pager system would handle mapping as it would always, copying data to and from the backing store as needed. The only change needed was for the pager to be able to hold several sets of mappings between RAM and store, one for each program using the system. The pager also held access time information in order to tune performance. The resulting pager was fairly complex, filling a full-height 19" rackmount chassis.
</p><p>One notable feature of TENEX was its user-oriented <a href="/facts/Command_line_interpreter/R9JpGmXQ">command line interpreter</a>. Unlike typical systems of the era, TENEX deliberately used long command names and even included non-significant <i>noise words</i> to further expand the commands for clarity. For instance, Unix uses ls to print a list of files in a directory, whereas TENEX used DIRECTORY (OF FILES). "DIRECTORY" was the command word, "(OF FILES)" was noise added to make the purpose of the command clearer.  To relieve users of the need to type these long commands, TENEX used a <i><a href="/facts/Command-line_completion/MFaxnWrl">command completion</a></i> system that understood unambiguously abbreviated command words, and expanded partial command words into complete words or phrases. For instance, the user could type DIR and the escape key, at which point TENEX would replace DIR with the full command. The completion feature also worked with file names, which took some effort on the part of the interpreter, and the system allowed for long file names with human-readable descriptions. TENEX also included a <i>command recognition</i> help system: typing a question mark (?), printed out a list of possible matching commands and then return the user to the command line with the question mark removed. The command line completion and help live on in current CLIs like <a href="/facts/Tcsh/ot248H7D">tcsh</a>.
</p>
<h2 id="from-tenex-to-tops-20">From TENEX to TOPS-20</h2>
<p>TENEX became fairly popular in the small PDP-10 market, and the external pager hardware developed into a small business of its own. In early 1970 DEC started work on an upgrade to the PDP-10 processor, the KI-10. BBN once again attempted to get DEC to support a complex pager with indirect page tables, but instead DEC decided on a much simpler single-level page mapping system. This compromise impacted system sales; by this point TENEX was the most popular customer-written PDP-10 operating systems, but it would not run on the new, faster KI-10s.
</p><p>To correct this problem, the DEC PDP-10 sales manager purchased the rights to TENEX from BBN and set up a project to <a href="/facts/Porting/7s6tFs8B">port</a> it to the new machine. At around this time Murphy moved from BBN to DEC as well, helping on the porting project. Most of the work centered on emulating the BBN pager hardware in a combination of software  and the KI-10's simpler hardware. The speed of the KI-10 compared to the PDP-6 made this possible. Additionally the porting effort required a number of new <a href="/facts/Device_driver/rDYnHU1G">device drivers</a> to support the newer backing store devices being used.
</p><p>Just as the new TENEX was shipping, DEC started work on the KL-10, intended to be a low-cost version of the KI-10. While this was going on, <a href="/facts/Stanford_University/JEQeF9z2">Stanford University</a> AI programmers, many of them <a href="/facts/MIT_alumni/ILzfbBHE">MIT alumni</a>, were working on their own project to build a PDP-10 that was ten times faster than the original KA-10. The project evolved into the <a href="/facts/Foonly/4Tmbot8P">Foonly</a> line of computers. DEC visited them and many of their ideas were then folded into the KL-10 project. The same year IBM also announced their own machine with virtual memory, making it a standard requirement for any computer. In the end the KL integrated a number of major changes to the system, but did not end up being any lower in cost. From the start, the new <a href="/facts/DECSYSTEM-20/G4C1vQ1m">DECSYSTEM-20</a> would run a version of TENEX as its default operating system.
</p><p>Functional upgrades for the KL-10 processor architecture were limited. The most significant new feature (called <i>extended addressing</i>) was modified pager microcode running on a <i>Model B</i> hardware revision to enlarge the user virtual address space.  Some effective address calculations by instructions located beyond the original 18-bit address space were performed to 30 significant bits, although only a 23-bit virtual address space was supported.  Program code located in the original 18-bit address space had unchanged semantics, for <a href="/facts/Backward_compatibility/FbHFBu5y">backward compatibility</a>.
</p><p>The first in-house code name for the operating system was VIROS (VIRtual memory Operating System); when customers started asking questions, the name was changed to SNARK so that DEC could truthfully deny that there was any project called VIROS. When the name SNARK became known, the name was briefly reversed to become KRANS; this was quickly abandoned when someone objected that "krans" meant "funeral wreath" in <a href="/facts/Swedish_language/1DkSIXkH">Swedish</a> (though it simply means "wreath"; this part of the story may be apocryphal).
</p><p>Ultimately DEC picked TOPS-20 as the name of the operating system, and it was as TOPS-20 that it was marketed. The <a href="/facts/Hacker_(programmer_subculture)/8ww6P79y">hacker community</a>, mindful of its origins, quickly dubbed it TWENEX (a <a href="/facts/Portmanteau/d124JEbz">portmanteau</a> of "twenty TENEX"), even though by this point very little of the original TENEX code remained (analogously to the differences between <a href="/facts/AT%2526T_Corporation/BfsX7eX2">AT&T</a> V7 Unix and <a href="/facts/Berkeley_Software_Distribution/XQKcURrh">BSD</a>). DEC people cringed when they heard "TWENEX", but the term caught on nevertheless (the written abbreviation "20x" was also used).<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a>
</p><p>TWENEX was successful and very popular; in fact, there was a period in the early 1980s when it commanded as fervent a culture of partisans as <a href="/facts/Unix/0pNL2seI">Unix</a> or <a href="/facts/Incompatible_Timesharing_System/SMuAEgUx">ITS</a>—but DEC's decision to scrap all the internal rivals to the <a href="/facts/VAX/N3r13IHH">VAX</a> architecture and its <a href="/facts/OpenVMS/rAnHAgpD">VMS</a> operating system killed the DEC-20 and put an end to TWENEX's brief period of popularity. DEC attempted to convince TOPS-20 users to convert to VMS, but instead, by the late 1980s, most of the TOPS-20 users had migrated to Unix. A loyal group of TOPS-20 enthusiasts kept working on various projects to preserve and extend TOPS-20, notably <a href="/facts/Mark_Crispin/PlEmFxy4">Mark Crispin</a> and the Panda TOPS-20 distribution.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Time-sharing_system_evolution/Smz9T1zn">Time-sharing system evolution</a></li></ul>

<ul><li>Some text in this article was taken from The Jargon File entry on "<a href="http://catb.org/~esr/jargon/html/T/TWENEX.html">TWENEX</a>", which is in the public domain.</li></ul>

<h2 id="further-reading">Further reading</h2>
<ul><li><a href="/facts/Daniel_G._Bobrow/GKssbwds">Daniel G. Bobrow</a>, Jerry D. Burchfiel, <a href="/facts/Daniel_Murphy_(computer_scientist)/wKz6xReT">Daniel L. Murphy</a>, <a href="/facts/Ray_Tomlinson/GlEKrATX">Raymond S.  Tomlinson</a>, "<a href="http://tenex.opost.com/tenex72.txt">TENEX, A Paged Time Sharing System for the PDP-10</a>", <i>Communications of the ACM</i>, Vol. 15, pages 135–143, March 1972.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Strollo, Theodore R.; Burchflel, Jerry D.; Tomlinson, Raymond S. (July 22, 1970). "Technical Details of the BBN Pager Model 701" (PDF). Bolt, Beranek and Newman. <a href="/wiki/Ray_Tomlinson" target="_blank">/wiki/Ray_Tomlinson</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>"TWENEX". <a href="http://catb.org/jargon/html/T/TWENEX.html" target="_blank">http://catb.org/jargon/html/T/TWENEX.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
</ol>

TENEX (operating system) open-in-new

TENEX (operating system)