CIO Blast from the Past: 40 years of Multics, 1969-2009
- 11 November, 2009 09:56
- Comments 2
![Multics lead developer and Turing Award winner, MIT's Professor Fernando J. Corbato [photo by Jason Dorfman, Creative Commons Attribution and ShareAlike licence]](http://cdn.idg.com.au/gim/id/21379/res/21)
Multics lead developer and Turing Award winner, MIT's Professor Fernando J. Corbato [photo by Jason Dorfman, Creative Commons Attribution and ShareAlike licence]
October 2009 marked an important milestone in the history of computing. It was exactly 40 years since the first Multics computer system was used for information management at the Massachusetts Institute of Technology.
Multics (Multiplexed Information and Computing Service) is regarded as the foundation of modern time-sharing systems. Multics was the catalyst for the development of Unix and has been used as a model of operating system design since its release four decades ago.
See related slideshow: CIO Blast from the Past: 40 years of Multics |
Professor Fernando J Corbato was the leader of the Multics project at MIT and also led the team that developed Compatible Timesharing System (CTSS) in 1961, one of the first timesharing systems and the research precursor to Multics.
In this edition of CIO Blast from the Past we talk to Fernando Corbato about the early days of Multics, why it was so influential, open source and software development practices, and how cloud computing is a modern incarnation of Multics’ time-sharing philosophy.
CIO’s Blast from the Past series has previously covered 60 years of cryptography and 110 Years of IBM technology.
1. Describe the early days of Multics research and development. What was it like developing a time-sharing system from scratch on mainframe computers?
One of the key reasons for developing Multics was the incredibly difficult programming environment we had in those days. There were only mainframe computers, and programming was typically done with punched cards and batch-processing runs. The prospect of time-sharing was proposed and eloquently advocated by John McCarthy.
At MIT we had already built CTSS (The Compatible Time-Sharing System) as a demonstration system. It was out of this environment that Project Mac was formed at MIT with the vision of exploring and enhancing interactive computing.
Multics was first described in six papers presented at the 1965 Fall Joint Computer Conference and its development is wonderfully chronicled at multicians.org by Tom Van Vleck.
Developing Multics turned out to be very hard, because after putting in all the hardware changes we needed for time-sharing, we found we had a significantly different machine, the GE 645. This in turn forced us to write a new assembler, and since we planned to program the system in a higher level language, a new compiler too.
We also were handicapped by the geographical dispersion, with our Bell Lab collaborators over 200 miles away in New Jersey and the GE Computer Division in Phoenix nearly 3000 miles away. The key thing that saved us was the availability of CTSS, which allowed remote access via telephone lines from the remote sites.
2. If you were tasked with doing the same again today, what would you have done differently? How do you think your approach would have been different?
We were convinced at the time we needed a higher-level language to program the bulk of the system to amplify the effectiveness of each programmer. I still think that was a wise decision.
In hindsight we might have picked a simpler language than PL/I, since it was a work in progress and no one had ever written a compiler for it when we started. Eventually, however, Bob Freiburghouse and a small team did some heroics and pulled it off several years later.
3. When Multics went live in October 1969 at MIT it quickly became the most widely used time-sharing system. What were some of the practical applications of Multics throughout the 40 years of its education and commercial use?
Multics was designed to be a general-purpose, time-sharing system so the focus was less on the novelty of the applications and more on the ease of developing and building applications and systems.
Probably the biggest legacy was Unix. [It was] superbly developed by Ken Thompson who, as one of the Multics developers was influenced by many of the Multics features, especially the hierarchical file system, file access controls and paging.
The biggest lack in Multics was graphical display technology in the terminals since display technology in the 1960's had not matured to the level we see today with personal computers.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Bookmark this page
- Share this article
- Got more on this story? Email CIO
- Follow CIO on twitter
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Face Time - Interview with John Brennan and Robert DiStefano
-
Phones are distractions during catch-ups
-
Google's Sidewiki lets people post comments about Web pages
-
Leaving your job? Take your data with you
-
Oracle x86 Rack Servers Optimized for Rapid Deployments and Operational Efficiency
Business-critical and mission-critical workloads demanding applications and databases require stable and secure environments. When these types of workloads are deployed on x86 servers, the need to ensure business continuity, maximum uptime, and consistent processing means that IT managers and business unit managers are looking at enterprise x86 servers in a new way: They realize that the business depends on these servers and that x86 server platforms for the enterprise are no longer expendable, as they might have been when servers were dedicated to a single application or when they were deployed as small Web servers that could be easily taken offline and replaced. -
A Data Center Fabric Is Critical to a Next-Generation Unified Data Center
The data center has gone through several major evolutionary changes over the past several decades, and each change has been defined by major shifts in computing. The shift to a virtual data center will be the single biggest transition in the history of computing. This transition will reshape all the major data center tiers: applications, storage, servers and the network. This paper examines the drivers of this transition, provides real-world case studies and includes data centre fabric best practices. -
Managing IBM License Complexity
IBM provides thousands of products in its portfolio and uses a variety of license models, contract terms and conditions. These license models can be very complex, causing frequent confusion for organisations trying to grasp the concepts while maintaining license compliance. While at first IBM licensing may seem incomprehensible, some education on the license models and licensing scenarios will help minimise the confusion. In addition, a more automated approach to managing licenses enables organisations to gain control, reduce ongoing software costs and minimise license liability risks. Read on.
Get exclusive access to Invitation only events CIO, reports & analysis. 
Comments
Anonymous
Dude, check your facts
MIT Multics did not shut down in 1998.
It shut down at midnight, January 1, the beginning of 1988.
Your facts are 10 years off...
I was the last user ever logged on to MIT Multics. Me, and the Operator account. I never even logged off MIT Multics, I let it wink me out as it was winked out.
Get yer facts straight.
Rodney Gedda
1988, not 1998
That error has been corrected in the article.
Thank you.
Post new comment