40 Years of Multics, 1969-2009 138
gribll writes "October 2009 marked an important milestone in the history of computing. It was exactly 40 years since the first Multics computer system was used at MIT. The interview is with Multics co-developer, MIT Professor and Turing Award winner Fernando J. Corbato. 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. There is also a picture gallery of Multics history."
Favorite quote (Score:5, Funny)
"In hindsight we might have picked a simpler language than PL/I, . . ." Now there's an understatement!
Re: (Score:2)
obKanye (Score:3, Funny)
Hey Multics, I'm really happy for ya, and imma let you finish, but UNIX is the best multiuser operating system of ALL TIME. OF. ALL. TIME.
Re: (Score:1, Offtopic)
Re: (Score:2, Insightful)
I don't get it. Kanye is probably the single lamest meme since the beginning of the Internet. And it's a even more lame media "scandal" that "nipplegate". By an order of a magnitude, at least.
Badger badger looks like deep Chinese philosophy, written in the words of Shakespeare, in comparison.
Can we get back to "In Soviet Russia, car is analogy of YOU" jokes, please? :)
Re: (Score:1, Offtopic)
Redundant?? I was the first and only one complaining about that at the time of submission.
Retarded moderators again?
Re: (Score:3, Insightful)
Bah. Unix is just Multics with the balls cut off.
Stupid Comment (Score:4, Interesting)
Professor Corbato got so many things right on the GE645 that he, Gordon Bell, Maurice Wilks and Tom Kilburn were the generation of _REAL_ uber-architects in the 60/70 s; with Gene Ahmdahl and Fred Brooks doing the engineering heavy lifting, Chris Streachy and and the MIT school (Marvin Minsky and many others) did the philosophy.
Without their contributions the Computer Industry would never have started
Re: (Score:2)
Re: (Score:2)
The GE645 design is contemporaneous with IBM's 7094, which ran CTSS at MIT before Multics replaced it. Gene Ahmdahl was working for IBM and designed the 360-architecture, Fred Brooks lead the OS 360 team and wrote the Mythical Man Month about his experiences. Ken and Tom Olsen, at DEC, thought that Custom Digital electronics was the way to go and DEC was the FLIP Chip company, and computers were "S
Re: (Score:2)
Your statements don't even make sense - DEC's products were general purpose computers, some of which were engineered in such as way as to be especially useful in a lab setting, but nonetheless general purpose computers. Yet you claim the guy who founded the company in the 50's and ran it for decades thought computers were "snake o
I wish it never died! (Score:5, Interesting)
I had to use it at a large energy company in Europe in the 1980s. It was actually a fantastic system.
Unlike VMS and IBM's mainframe OSes, it was actually pretty friendly to use. This attribute has clearly rubbed off on UNIX. While we'd spend months teaching some users how to use VMS, they'd get Multics within a few days.
The programming environment was also fantastic. It didn't support as many languages as VMS, nor did it have language interoperability that was as good, but it still supported more languages than you'd fine on typical UNIX systems of that era.
That said, it still was a beast compared to UNIX. UNIX was sly and sleek, and thus supported lower-end hardware better than Multics could. And UNIX was more portable, which eventually made it more widely available.
Still, I look upon my Multics days with a fondness I didn't find again until the early 2000s, when I was able to get a position administering a network of FreeBSD servers.
Re: (Score:3, Interesting)
My recollection from the early 80s is that it had fantastic language interoperability, especially compared to other systems at the time.
On Multics you could pass variables from one language to another using full declarators allowing each language to inspect the value and type and more of each incoming variable, and act accordingly, and most of the Multics languages supported that in the compiler.
So PL/I could call into FORTRAN and on and on.
It's been a long time, I could easily be wrong about this, but that
Re: (Score:2, Informative)
I think you're thinking of VMS.
Depending on the languages being interfaced, MULTICS requires the marshaling to be done manually. It wasn't complex code, by any means, but a set of wrapper routines and data translation routines were needed.
Some implementations didn't require that, however. When I used MUTLICS, we wrote our code in a mix of ALM, PL/1, COBOL and FORTRAN. The COBOL and FORTRAN compilers were from the same vendor, and supported immediate interoperability. The PL/1 compiler was from a different v
Re: (Score:3, Informative)
If I need help, I type "help". If I need to copy a file, the command is "copy". If I want to rename a file, guess what the command is? You guessed it - "rename"
Plus, the uptime is tremendous, which is a VERY friendly attribute.
Re: (Score:2)
Re: (Score:3, Interesting)
Re: (Score:2)
The ability to "copy" a file without having to worry about it's type put Unix way ahead. And real hierarchial directories with a sensible syntax without different rules for the levels! (something that Microsoft refuses to learn after decades...)
I was very impressed, having come from using VMS for about 2 years before I started on Unix (I was at Dec and they had a small VAX running BSD because they wanted to port a CLU compiler from it to VMS). This was 1982.
The commands were cryptically short, so I certainl
Re:I wish it never died! Revisited (Score:2)
but remember, "BLISS is IGNORANCE" all those '.' s, Duh! PDP-10 Algol was written in BLISS by Wolf from CMU,
and reading it made the head hurt.
A final thought, why can not manufacturers write working assemblers, and more linkers for their platform,
all the industry stuff, except the PDP-10 assembler (aka MASM in modern terms) and all manufacturer linkers
have been crap!
BTW the reason C was a mess is that Ken Olsen's brother wanted it so; an
Re: (Score:2)
The Damned Command Language? I remember when they added that to RSTS/E. I hated it. Overly verbose but you could abbreviate it by just typing the first few characters of the command so it wound up being completely cryptic in practice.
Re:I wish it never died! (Score:4, Informative)
Essentially I think VMS had a shallow learning curve where Unix was pretty steep, but the shallow curve meant it took you longer to learn how to do really powerful things. The result was that it was faster to become a functional user with VMS, but you got to be a power user more quickly with Unix.
Re: (Score:2)
You talk about VMS in past tense, but I use it every day. Along with Windows, and Unix. I code in C and in Java (J2EE, Spring). Eclipse works well for writing both because its syntax highlighting and call hierarchy features cope well with extensions they don't know about (Pro*C, and VMS libraries).
Not all the old systems are dead.
Re: (Score:2)
Another big factor is that back then, short variable names were common, and often required. Thus your typical 6 letter function and variable names (strcpy). Sometimes it's worse, if your company has some naming conventions. So programmers tended to think tersely.
Combine that with limited program file name lengths as well. Each Unix command was a real file name, not just strings in a CLI parser.
Re: (Score:2)
You are cxomparin
Re: (Score:2)
You are cxomparing Multics (1970 hardware and software)
OK (started in the late 1960's, but mostly 70's)...
with Unix (1980 hardware and software)
Well, I guess the flurry of "1) pick a microprocessor 2) build/buy a UNIX port 3) ??? 4) Profit!" machines was mainly in the 1980's, kicked off by AT&T's binary licensing of V7, but UNIX dates back to the 1970's as well, on the originated-in-the-1970's PDP-11.
and VMS (1990 hardware and software)
Erm, try "VMS (late 1970's hardware and software)" - the VAX, and VMS, came out in the late '70's.
Re: (Score:2)
That said, it still was a beast compared to UNIX. UNIX was sly and sleek, and thus supported lower-end hardware better than Multics could. And UNIX was more portable, which eventually made it more widely available.
That's an understatement. In the early 70's I was running Unix on a PDP-11/34 with 28K of ram and a 5MB hard disk, eventually using it to run an Evans & Sutherland PS1.
Um, wasn't bloated Multics the reason *WHY* . . . (Score:3, Insightful)
. . . Thompson and Richie decided to start a less ambitious project, called Unix?
Re:Um, wasn't bloated Multics the reason *WHY* . . (Score:4, Insightful)
Yeah, that "was the catalyst" line is great. You can come up with all sorts of equivalent expressions. Like "MS-DOS was the catalyst for Linux", or "horse manure was the catalyst for the automobile"
Re: (Score:1)
"horse manure was the catalyst for the automobile"
Just because it couldn't be more off-topic, The Horse & the Urban Environment [enviroliteracy.org] describes this relationship quite well.
Re: (Score:2)
Come on, MS-DOS was the best operating system MicroSoft ever produced!
Re: (Score:3, Insightful)
It was a shameless CP/M knock-off produced by some hole-in-the-wall called Seattle Computer Products. MS bought it for $50,000 and proceeded to destroy the brilliant company known as Digital Research who developed the real thing (CP/M, later DR-DOS). DR also had a better GUI environment than early versions of Windows called GEM. I remember GEM fondly on my Atari ST. Ran it on a 286 for a while too.
Re: (Score:2)
Mini-meme alert: There fixed that for you. QDOS [wikipedia.org]
Re: (Score:2)
That and they like what Multics offered but didn't have the hardware to support it.
Of course the Current version of Linux or BSD is probably more "bloated" then the last version of Multics.
Re: (Score:1, Informative)
Yes: the Multics kernel was 250 K (I'm not sure if that's thousand words or thousand bytes, but keep in mind that this was the era of 36-bit words and 9-bit bytes) in 1983. Multicians.org has all the classic legends and misconceptions here: http://multicians.org/myths.html#slow
Re: (Score:2)
That is 250K SLOC. SLOC stands for Significant lines of code. Heck I have seen applications that rival that. Multics was small and looks pretty light. To bad it was impossible to have written it in c instead of PL/1. Had it been in c it might still be around and useful.
Multics predates c BTW so it couldn't have been written in c. It could have been ported maybe but by then we had Unix.
Re: (Score:2)
Actually there were not really any "bytes" at all, as in addressable units smaller than the 36-bit word.
Various software would store ASCII in the words in different ways, using 6x6, 7x5, or 4x9 bits for them.
Re:Um, wasn't bloated Multics the reason *WHY* . . (Score:4, Funny)
Of course the Current version of Linux or BSD is probably more "bloated" then the last version of Multics.
Sure, trade in a 40 year old operating system for two 20s, just because its a little bloated after giving you the best years of its life... Does this tty driver make my kernel look fat?
Re: (Score:2)
Hey whats wrong with getting a trophy OS. You know an OS can never be too thin or too new :)
Re:Um, wasn't bloated Multics the reason *WHY* . . (Score:5, Insightful)
Re:Um, wasn't bloated Multics the reason *WHY* . . (Score:4, Insightful)
It turned out that UNIX, while inferior, was good enough for a lot of things...
It's amazing the number of times in computing where something, while inferior, was good enough for a lot of things and ended up dominating...
Not limited to computing... (Score:1)
It's amazing the number of times in computing where something, while inferior, was good enough for a lot of things and ended up dominating...
It's a demonstrable effect in most industries really. McDonald's is a perfect example. "Good enough" seems to be the sweet spot for garnering mass appeal.
Re: (Score:3, Interesting)
"It's amazing the number of times in computing where something, while inferior, was good enough for a lot of things and ended up dominating..."
And it's also amazing the number of times that "inferior but good enough" product, after dominating the low-end field due to its small and lightweight design, then has to scale up by painfully and clumsily reintroducing all the "bloated" features of the higher quality and better-designed product. And then of course, makes the better product extinct not on its own mer
Re: (Score:2)
A little late for replying, but anyway...
You can even go further back in time : the concept of channels for IO processing separate from the CPU is still no standard in the x86 world. The fact that IO speed is still a bottleneck is still not recognised. Instead faster processors are pushed, but never matched with better IO.
Re: (Score:3, Insightful)
Re: (Score:2)
"Bloated"? Oh, FFS. (Score:4, Funny)
It's true that Multics couldn't get out of its own way on a system with 64K of RAM, although it was technically supposed to run on that configuration. To work well, it really wanted several hundred K of RAM. Thank heavens we left it in the dustbin of history, replaced by the crisp, clean efficiency of Windows, or OS X, or Linux.
If memory serves... (Score:2)
Re: (Score:2)
Pretty sure it's a play on a different word:
Multics: multiple
Unix: one (latin: unus)
40 Years of Multics, 1969-2009 (Score:5, Interesting)
Re: (Score:3, Insightful)
Re: (Score:2)
Ken answered
Re: (Score:2)
KISS (Keep It Simple)
You'd think "Keep It Simple" would be abbreviated "KIS" ;)
Re: (Score:1, Funny)
Re: (Score:2, Informative)
KISS = Keep It Simple Stupid !
Re: (Score:2)
KISS (Keep It Simple Stupid)
Re: (Score:1)
Maybe he just wanted to provide the Keep It Simple and was hoping you'd provide the Stupid?
Re: (Score:1)
The phrase itself was used as a stupid detector, eh?
Security in hardware (Score:3, Interesting)
When I worked at the Pentagon (HQAF DSC) one of the machines I developed on was a Multics machine. The really interesting part of the architecture to me was that it had, if I recall correctly, seven permission rings from ring 6 to ring 0 and each were implemented in hardware. The OS ran on a separate processor cluster for each ring, and system level work (kernel mode) was done all in ring 0.
I enjoyed learning PL1, and found it to be an easy transition to go to Unix/C. The multics box was a beast, and stuff ran like greased lightning.
Slashdot is bad with anniversaries (Score:5, Funny)
and they waited until november to tell you!
Re: (Score:2)
I hope that, at the very least, someone sent MULTICS a very nice "I'm sorry I forgot your birthday" card. Something cute, perhaps with sad puppies.
OTOH, MULTICS is 40. I know I wanted everyone to forget my 40th birthday.
Re: (Score:2)
It would be cool if somebody could get one running somewhere and hook it up to an internet connected box. Maybe you could ssh into a BSD box then cu into the MULTICS box and get a feel for how it works.
Forty-year anniversaries -- what connection? (Score:3, Funny)
So I've got to ask, does this have any synchronic significance with the recent 40-year anniversary of Sesame Street [google.com] recently splashed around Google's main page?
Hmm... "This episode brought to you by the letters P, L, and I, and the number pi!" :)
Cheers,
Lots of 1969 anniversaries (Score:1)
The moon landing, the Internet, Multics, and lots of other things.
Re: (Score:2)
Boeing 747, "In the Court of the Crimson King", "Led Zeppelin I", "Ummagumma", "Deep Purple", the Woodstock Festival, Monty Python's Flying Circus, last public performance of the Beatles, Sesame Street... Any others?
If it was so good (Score:3, Interesting)
If it was so good, then why aren't there any emulators for it? Nearly every other old system has emulators, but not Multics.
Re: (Score:3, Interesting)
A few people are trying to get emulators going, the biggest problem is the lack of documentation of the peripheral hardware interfaces used on Multics capable systems. Check out the archives of the alt.os.multics news group.
Re: (Score:2)
Just don't look at any binary posts by 'uncle_buck'.
Re:If it was so good (Score:4, Interesting)
There are a few defunct projects on sourceforge and, I think, one live effort. I'm writing an emulator, but I haven't released any code yet.
CPUs are trivial. Systems can be hard.
Writing an emulator probably wasn't feasible before the sources were released two years ago. A few people started prior to that, but I can't imagine how.
Multics ran on somewhat complex hardware. In addition to the CPU, there were several other complex components including the system controllers, I/O multiplexors, and front end processors. Some of these were programmable or semi-programmable devices and much of the documentation is missing.
Now that we have compiler listings, assembly listings, a few documents, and a boot tape, the task seems feasible. Digging through the machine code on the boot tape and in the assembly listings partially makes up for the lack of decent documentation on some of the components.
My emulator is far from complete -- and it's almost 18K lines of code. It does read the boot tape and run about 2 million instructions, but crashes before finishing the boot process. The emulator doesn't yet know about disks or support instruction restart etc. There's a lot of work left to do.
I plan on cleaning up a few things and releasing it real soon now.
Re:If it was so good (Score:4, Funny)
Re:If it was so good (Score:4, Informative)
Re: (Score:2)
Were there any games for it?
"Cancel the call for the company nurse" (Score:1)
Good thing they didn't call it Unics or it would've been the butt of jokes for decades.
Re: (Score:1)
First introduction to viruses (Score:5, Interesting)
I have a feeling that this "feature" got removed very soon after it snarfed the Computer Unit Director's screen.
Re: (Score:1)
Chris Tavares wrote the original Cookie Monster program in 1970. Story is at http://www.multicians.org/cookie.html -- sounds like you used a descendant of the original. Source is available online. The program did not wander randomly: you had to start it while logged in, and it would then sleep and pop up messages later. People used to prank their co-workers when they found a terminal unattended.
Re: (Score:2)
I remember seeing that in the documentary [imdb.com].
What was Multics used for? (Score:2)
I remember reading that Multics was going to be the OS used to provide computing-as-utility; everyone was just going to be able to use it. Did this plan ever pan out (was Tymnet and Telenet Multics-based?) Who, then, were the Multics customers and what, if anything, spawned from it (other than Unix and VisiCalc, as mentioned in TFA)?
K.T (Score:2)
Re: (Score:2)
Can you (Score:4, Insightful)
Can you really rate it as 40 years, since the last operational site was shut down in 2000? Shouldn't the timer stop when it dies, like with people? Do you give Columbus's age as over 500 years?
Re: (Score:2)
Must have been a sad life, after you asked your parents why they didn't celebrate your birthday, and they answered: "We will celebrate, when you're dead!" :P
Real-Time, too! (Score:3, Funny)
As Roger Needham [wikipedia.org] quipped, Multics was design for the real-time processes of geological processes.
The Michigan Terminal System... (Score:2)
...came first.
I was a Multics user and code developer (Score:4, Interesting)
I still miss the clean user interface (all command-line arguments meant the same thing, no matter which command was being executed) and fine documentation. But the GE645 / Honeywell 6800 architecture was never well-enough documented to make emulation feasible. And the descendants of Multics have implemented most of the features more-or-less. The world has moved on.
I've moved on, too. In 1978 I taught myself C; I've since learned and continue to program in C++, Java and Python, having discarded along the way Lisp, Pascal and Delphi.
And I use Windows mostly now. But my memory tells me that Multics was often faster for routine things like searching the file system. (Though the filesystem back then was only a few hundred MB.) And the processor back then was good for about 1 MIPS. Forget about color graphics. Animation? That was for cartoonists.
Anyway, this old-timer got a chuckle out of the article; thanks for posting the heads-up.
Re: (Score:2)
People like you really need to post here more often.
Re: (Score:2)
IF IF = THEN THEN THEN = ELSE; ELSE ELSE = IF;
Re: (Score:2)
I thought about it for a while, and then I finally gave up after developing a headache. How could that possibly be legal unless you could just throw variable names in wherever a variable would be.....
IF X = Y THEN Y = Z; ELSE Z = X;?
it would eventually loop....
x86 segmentation and Multics (Score:1)
Re: (Score:2)
Multics, comp.risks, and NSA (Score:1)
I think this is irony, but I'll still share... (Score:1)
Antithesis (Score:2)
Like many other posters, I too was a Multician at university. It rocked. But I prefer my nice GUI and not having to share my processo
cool story (Score:2)
Re: (Score:1)
Re: (Score:1)
Re: (Score:1, Funny)
Singer made farming equipment?
Re: (Score:2)
The last time I saw punch cards in use was in the late 1990's. Granted this was more of a reuse, the "users" were my Geology professors. A three or four inch tall stack of punch cards with thick straight lines from a marker on the edge of the stack worked well as a model for rock deformation when the stack was flexed. Oh, you mean using punch cards in a computer, no, I've never seen that.
Re: (Score:2)
I started work in the early 90s, and I only missed them by a year or so.
I do remember seeing the output from the C**** compiler there and noting that it was older than I was.
NGOML!
Re:Hmm, Multics and Sesame Street, both 40 years o (Score:4, Funny)
This episode of Multics was brought to you by the letters P and L and the number 1
Re:Hmm, Multics and Sesame Street, both 40 years o (Score:2)
Yes... That is what a Coincidence is. When 2 things that seem to have a connection while they don't