Slashdot Mirror


40 Years of Multics, 1969-2009

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."

138 comments

  1. Favorite quote by alecto · · Score: 5, Funny

    "In hindsight we might have picked a simpler language than PL/I, . . ." Now there's an understatement!

    1. Re:Favorite quote by ehrichweiss · · Score: 1

      Yeah, you're not kidding. PL/1 was one of the first languages I learned back in the early 80's and I'm ever so glad that I never had to put that knowledge to any real use other than academics. Though I did find my old box of programming manuals from back then and right on top was my PL/1 and APL manuals from IBM. I wonder if those are worth anything these days...

      --
      0x09F911029D74E35BD84156C5635688C0
    2. Re:Favorite quote by Anonymous Coward · · Score: 1, Funny

      As Multics begat UNIX, PL/I lives on within the development community of .... SAS.

  2. Remember punch cards by jessica77 · · Score: 0, Offtopic

    I have a fellow in my office who cannot seem to stop talking about punch cards, he also has a dilbert cartoon for it. Life has changed so much with the advent of computers, especially the desktop PC's / MACs

    1. Re:Remember punch cards by rotorbudd · · Score: 1

      Punch cards on a Singer,,, yes the sowing machine company,,,mainframe.

      --
      A bullet may have your name on it, but artillery is addressed to " Whom It May concern"
    2. Re:Remember punch cards by hammarlund · · Score: 1

      Sure, punch cards, and I also remember paper tape that used to write from and read to teletype terminals connect to an IBM 360 or something back in college. How old am I?

    3. Re:Remember punch cards by Tycho · · Score: 1

      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.

      --
      Impersonating Tycho from Penny Arcade since before there was a PA.
    4. Re:Remember punch cards by Hognoxious · · Score: 1

      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!

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    5. Re:Remember punch cards by Anonymous Coward · · Score: 1, Funny

      Singer made farming equipment?

    6. Re:Remember punch cards by Anonymous Coward · · Score: 0

      Is it me, or are the trolls getting more spammier of late?

  3. obKanye by Fortunato_NC · · 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.

    --
    Blogging Weight Loss, Distance Education, and more at verlin.com
    1. Re:obKanye by Finallyjoined!!! · · Score: 0, Offtopic

      Huh? youa noa speaka noa sensea!.

      --
      If I had an Ass, I'd call it Fanny Bottom, then I could slap my Ass; Fanny Bottom, on the Arse.
    2. Re:obKanye by Anonymous Coward · · Score: 0

      Nah plan 9 kick unix ass

    3. Re:obKanye by Hurricane78 · · 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? :)

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    4. Re:obKanye by Hurricane78 · · Score: 0, Offtopic

      Redundant?? I was the first and only one complaining about that at the time of submission.

      Retarded moderators again?

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
    5. Re:obKanye by R3d+M3rcury · · Score: 2, Insightful

      Bah. Unix is just Multics with the balls cut off.

    6. Re:obKanye by Anonymous Coward · · Score: 0

      Preemptive multitasking fuck yeah

    7. Re:obKanye by goose-incarnated · · Score: 0, Offtopic

      Redundant?? I was the first and only one complaining about that at the time of submission.

      Retarded moderators again?

      Now thats redundant :-)

      --
      I'm a minority race. Save your vitriol for white people.
  4. MULTICS by Anonymous Coward · · Score: 0

    Multiple Useless Large Tables In Core Simultaneously.

  5. I wish it never died! by Anonymous Coward · · 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.

    1. Re:I wish it never died! by Anonymous Coward · · 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's what I remember.

    2. Re:I wish it never died! by Anonymous Coward · · 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 vendor, and required us to write very simple bindings.

    3. Re:I wish it never died! by joebagodonuts · · Score: 2, Informative

      VMS isn't "friendly to use"? Really? I guess maybe it isn't if English isn't your first language, but what could be more friendly than DCL?
      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.

      --
      "Give a woman two glasses of wine and some pad thai, and they'll agree to just about anything." the Sports Guy
    4. Re:I wish it never died! by joebagodonuts · · Score: 1

      Perhaps you meant MVS? MVS is downright hostile!

      --
      "Give a woman two glasses of wine and some pad thai, and they'll agree to just about anything." the Sports Guy
    5. Re:I wish it never died! by raftpeople · · Score: 2, Interesting

      I was wondering the same thing. UNIX more friendly than VMS? Huh? UNIX has some positive things going for it, but of all of the command line operating systems I've used, it's actually towards the bottom of user friendly-ness.

    6. Re:I wish it never died! by spitzak · · Score: 1

      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 certainly immediatly added "alias" for everything to get the commands I was familiar with. However I disagree about help, the "man" pages were enormously more useful than anything VMS "help" ever coughed up. Also it was about 100 times easier to write working C programs (on VMS it was easier to translate C into BLISS than to try to get a C program to link).

      I did like the VMS editor better. I'm not even sure what I edited with on the Unix machine, it may have been vi? Or even TECO.

    7. Re:I wish it never died! by Darinbob · · Score: 3, Informative

      Hmm, I always considered VMS to be more user friendly, at least to novices, than Unix. Unix was full of cryptic shorthand commands. Ie, "help" vs "man -k", "search" vs "grep", "edit" vs "vi" or "ed" or "ex", etc. DCL was very quick to pick up compared to Unix sh, even though sh had more power.

      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.

    8. Re:I wish it never died! by syousef · · Score: 1

      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.

      --
      These posts express my own personal views, not those of my employer
    9. Re:I wish it never died! by Anne+Thwacks · · Score: 1
      Multics was so fantastic that I was able to crash the whole system by declaring an array called "ARRAY" in Fortran, (reboot required) and numerous other "obvious" blunders. (I am talking about 1972-4). A multi-user system that crashes because of accidental misuse of reserved words is not "user-friendly". I wrote my data capture programs in Basic, and heavy maths (wave equations) in Fortran - Multics certainly had inter-language support in the early 1970's - 20 years before the VAX and VMS.

      You are cxomparing Multics (1970 hardware and software) with Unix (1980 hardware and software) and VMS (1990 hardware and software) - these are cross generational comparisons. Try comparing Zyl with a Mercedes R class (obligatory Russian car analogy)

      --
      Sent from my ASR33 using ASCII
    10. Re:I wish it never died! by Have+Brain+Will+Rent · · Score: 1

      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.

      --
      The tyrant will always find a pretext for his tyranny - Aesop
    11. Re:I wish it never died! by crunzh · · Score: 1

      Why would you list uptime? I dont care if my system is rebooted everynight, as long as its up when I need it to be up.

      --
      Visit http://www.crunzh.com/ for free software. Mac/Lin/Win
    12. Re:I wish it never died! by Guy+Harris · · Score: 1

      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.

    13. Re:I wish it never died! by putaro · · Score: 1

      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.

    14. Re:I wish it never died! by SonnyDog09 · · Score: 1

      Unix was full of cryptic shorthand commands. Ie, "help" vs "man -k", "search" vs "grep", "edit" vs "vi" or "ed" or "ex", etc.

      I worked on multics systems for a few years back in the 80s. I loved the logical command names in multics. I hate the baby-talk nonsense that passes for command names in eunuchs. And the eunuchs think that they are *so cool* because they can use "grep" and "awk" like they are real words. If I want to display the contents of a file on a multics terminal, I type "show_file baz.foo" or "sf baz.foo". Even the abbreviations for commands make sense. Why the eunuchs think that the command "cat baz.foo" makes sense to perform this same function is something that I never got. Get off my lawn!

      --
      Your "fair share" is NOT in my wallet.
    15. Re:I wish it never died! by Mr.+Slippery · · Score: 1

      Why the eunuchs think that the command "cat baz.foo" makes sense to perform this same function is something that I never got.

      "cat" does not do the same thing as a "show_file" command. "cat" concatenates files: "cat file1 file2 > file3".

      --
      Tom Swiss | the infamous tms | my blog
      You cannot wash away blood with blood
    16. Re:I wish it never died! by Darinbob · · Score: 1

      The difference is partly the intended audience. Unix was written for the authors' use and their colleagues.

      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.

  6. Um, wasn't bloated Multics the reason *WHY* . . . by PolygamousRanchKid+ · · Score: 2, Insightful

    . . . Thompson and Richie decided to start a less ambitious project, called Unix?

    --
    Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
  7. If memory serves... by Thelasko · · Score: 1

    Unix (Eunuchs) is the castrated version of Multics.

    --
    One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    1. Re:If memory serves... by iroll · · Score: 1

      Pretty sure it's a play on a different word:
      Multics: multiple
      Unix: one (latin: unus)

      --
      Repetition does not transform a lie into the truth. - FDR
    2. Re:If memory serves... by Anonymous Coward · · Score: 0

      It's both. Ken Thompson was aware of the inferiorities of his design with respect to security.

  8. Re:Um, wasn't bloated Multics the reason *WHY* . . by timster · · Score: 3, 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"

    --
    I have seen the future, and it is inconvenient.
  9. Hmm, Multics and Sesame Street, both 40 years old. by Anonymous Coward · · Score: 0

    Coincidence ? I think not!

  10. 40 Years of Multics, 1969-2009 by omar.sahal · · Score: 4, Interesting

    Multics was very influential, it provided Ken Thompson an example of what not to do. In other words, stick closely to the KISS (Keep It Simple) principle.

    1. Re:40 Years of Multics, 1969-2009 by TheRaven64 · · Score: 2, Insightful

      Not really. Most of the features of Multics were eventually added to UNIX derivatives, but because they were added piecemeal by various different vendors over the years, they lack the coherence that they had on Multics.

      --
      I am TheRaven on Soylent News
    2. Re:40 Years of Multics, 1969-2009 by CannonballHead · · Score: 1

      KISS (Keep It Simple)

      You'd think "Keep It Simple" would be abbreviated "KIS" ;)

    3. Re:40 Years of Multics, 1969-2009 by Stupid+McStupidson · · Score: 1, Funny

      Well, it's better than: "KIS,YSFM"

    4. Re:40 Years of Multics, 1969-2009 by Anonymous Coward · · Score: 2, Informative

      KISS = Keep It Simple Stupid !

    5. Re:40 Years of Multics, 1969-2009 by Anonymous Coward · · Score: 0

      You may want to keep in mind that the UNICS name (originally spelled that way) was chosen, indeed, because Ken Thompson figured he was neutering Multics. As such, your post is seriously a gross mischaracterisation. C and Unix were originally designed to be what worked at the time: nothing but pure klugetastic hacks. No one expected AT&T to turn around and say "Hey, let's sell it!" when it became popular at Bell Labs.

    6. Re:40 Years of Multics, 1969-2009 by omar.sahal · · Score: 1

      Sorry I meant
      KISS (Keep It Simple Stupid)

    7. Re:40 Years of Multics, 1969-2009 by omar.sahal · · Score: 1
      Firstly I have never used Multics, so I can not directly comment on its superiority (or lack thereof) over Unix. However according to a interview for Unix: An Oral History

      Various accounts I’ve read of UNIX, Ritchie’s retrospective on it, and even an interview you did with some people for a video back in 1981 talk about the system as being, or UNIX as being, sort of culling all the best ideas in operating systems that emerged during the ‘60’s.

      Ken answered

      My background for obtaining these ideas was .... I worked on CTSS, I used CTSS per say. I used CTSS and did some, a lot of programming on CTSS and I worked on MULTICS.

    8. Re:40 Years of Multics, 1969-2009 by pregister · · Score: 1

      Maybe he just wanted to provide the Keep It Simple and was hoping you'd provide the Stupid?

    9. Re:40 Years of Multics, 1969-2009 by Tablizer · · Score: 1

      The phrase itself was used as a stupid detector, eh?

  11. Re:Um, wasn't bloated Multics the reason *WHY* . . by LWATCDR · · Score: 1

    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.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  12. Re:Um, wasn't bloated Multics the reason *WHY* . . by TheRaven64 · · Score: 4, Insightful

    Bloat isn't really the right word. Multics had a lot more features than UNIX, and some really nice ideas (like the fact that files and memory used the same interface), but it required very high-end hardware for the time. It was a mainframe OS. It would not run on a minicomputer and so UNIX was written to port a game from Multics to the spare minicomputer that Thompson and Richie had access to. It turned out that UNIX, while inferior, was good enough for a lot of things, but saying Multics is bloated compared to UNIX is like saying Linux is bloated compared to MS DOS 3.

    --
    I am TheRaven on Soylent News
  13. Security in hardware by Anonymous Coward · · 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.

    1. Re:Security in hardware by Anonymous Coward · · Score: 0

      Our Supervisor, who art in Ring 0,
      Multics be thy name.
      Thy booting come, thy commands be done,
      In absentee as it is in interactive.
      Give us this day our daily quota,
      And forgive us all our ring violations,
      As we forgive those who bump us.
      And lead us not into ring 7,
      But deliver us from GCOS.
      For Thine is the root and the MIP rate and the hierarchy
      Forever and ever (or until the next release).
      Foo.

    2. Re:Security in hardware by Anonymous Coward · · Score: 0

      The Overseer is my shepherd,
      I shall not get bumped.

      He maketh me to handle QUITs gracefully,
      He leadeth me past all error conditions.

      He restoreth my stack frame.
      He leadeth me into inner rings for my process's sake.

      Yea, though I walk through the valley of the shadow of GCOS,
      I will fear no preemption, for the Initializer is with me.
      ACLs and AIM, they comfort me.

      He preparest a process before me in the presence of other users.
      He anointest my session with guaranteed_login,
      My quota never runneth over.

      Surely security and data integrity will follow me all the days
      of my registration, and I shall dwell in the house of MULTICS
      forever.

  14. Slashdot is bad with anniversaries by Yvan256 · · Score: 4, Funny

    October 2009 marked an important milestone in the history of computing

    and they waited until november to tell you!

    1. Re:Slashdot is bad with anniversaries by idontgno · · Score: 1

      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.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    2. Re:Slashdot is bad with anniversaries by MichaelSmith · · Score: 1

      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.

  15. Re:Um, wasn't bloated Multics the reason *WHY* . . by Anonymous Coward · · 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

  16. "Bloated"? Oh, FFS. by jeffb+(2.718) · · Score: 3, 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.

  17. Forty-year anniversaries -- what connection? by zooblethorpe · · Score: 2, Funny

    So I've got to ask, does this have any synchronic significance with the recent 40-year anniversary of Sesame Street 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,

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."
  18. Lots of 1969 anniversaries by davidwr · · Score: 1

    The moon landing, the Internet, Multics, and lots of other things.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:Lots of 1969 anniversaries by harry666t · · Score: 1

      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?

    2. Re:Lots of 1969 anniversaries by Bitmanhome · · Score: 0, Redundant

      First man on the friggin' MOON, if that sort of thing is important.

      --
      Not that this wasn't entirely predictable.
    3. Re:Lots of 1969 anniversaries by Anonymous Coward · · Score: 0

      Jackson Browne's 21st birthday.

      I had to make simplifying assumptions. "In sixty-five I was seventeen.."

  19. If it was so good by SnarfQuest · · 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.

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    1. Re:If it was so good by cruff · · Score: 2, 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.

    2. Re:If it was so good by Gilmoure · · Score: 1

      Just don't look at any binary posts by 'uncle_buck'.

      --
      I drank what? -- Socrates
    3. Re:If it was so good by Darkness404 · · Score: 3, Informative

      Well, for one theres little need and for another there is little interest. The source code for Multics wasn't released till 1992, by then it was clear that UNIX was the future, development basically stopped for Multics long before then and Linux was beginning its rise as an open source UNIX system. With no legacy software to drive a tricky system to emulate why do it? I mean, with game consoles there are the games, with PC things usually there are a few nifty pieces of software, with Multics just about everything was ported to UNIX.

      --
      Taxation is legalized theft, no more, no less.
    4. Re:If it was so good by mike.mondy · · 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.

    5. Re:If it was so good by Anonymous Coward · · Score: 0

      People that used Multics "in the day" are ~50 - 60 years old now. Who wants a Multics emulator when you're too busy throwing rocks at kids and telling them to get off your lawn.

    6. Re:If it was so good by Hognoxious · · Score: 3, Funny

      Just in time to compete with HURD.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    7. Re:If it was so good by Hatta · · Score: 1

      Were there any games for it?

      --
      Give me Classic Slashdot or give me death!
  20. Re:Um, wasn't bloated Multics the reason *WHY* . . by LWATCDR · · Score: 1

    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.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  21. "Cancel the call for the company nurse" by davidwr · · Score: 1

    Good thing they didn't call it Unics or it would've been the butt of jokes for decades.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
    1. Re:"Cancel the call for the company nurse" by Megane · · Score: 1

      Nah, they would have just renamed it to "Urectumix".

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  22. First introduction to viruses by petes_PoV · · Score: 4, Interesting
    The implementation we used (SWURCC, England. 1978 - ?) had a "cookie monster" program. Briefly, this was a process that wandered randomly around the logged in users, occasionally taking control of their VDU and sending the message "I wanna cookie" It would only give you your screen back once the user typed "cookie". Swearing at it got you disconnected.

    I have a feeling that this "feature" got removed very soon after it snarfed the Computer Unit Director's screen.

    --
    politicians are like babies' nappies: they should both be changed regularly and for the same reasons
    1. Re:First introduction to viruses by thvv · · 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.

    2. Re:First introduction to viruses by Just+Some+Guy · · Score: 1

      I remember seeing that in the documentary.

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:First introduction to viruses by Anonymous Coward · · Score: 0

      I am thw and I am wearing teh baggyest pants EVAHR!!!!

  23. Re:Um, wasn't bloated Multics the reason *WHY* . . by Anonymous Coward · · Score: 0

    Horse manure is not a catalytic converter for automobile. That's just pure horseshit.

  24. What was Multics used for? by wandazulu · · Score: 1

    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)?
     

  25. K.T by MrKaos · · Score: 1

    Later in his career Ken Thompson had corrective eye surgery, changed his name to Kim Thayil and was the lead guitarist of Soundgarden...What an amazing talent.

    --
    My ism, it's full of beliefs.
    1. Re:K.T by Jerrry · · Score: 1

      Damn, and all this time I though Thompson and Ritchie retired from Bell Labs and formed ZZ Top.

  26. Can you by SnarfQuest · · 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?

    --
    Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    1. Re:Can you by Hurricane78 · · Score: 1

      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

      --
      Any sufficiently advanced intelligence is indistinguishable from stupidity.
  27. Re:Um, wasn't bloated Multics the reason *WHY* . . by Anonymous Coward · · Score: 0

    That was horrible. Seriously. Stop trying.

  28. Re:Hmm, Multics and Sesame Street, both 40 years o by satellite17 · · Score: 4, Funny

    indeed,

    This episode of Multics was brought to you by the letters P and L and the number 1

  29. Re:Hmm, Multics and Sesame Street, both 40 years o by jellomizer · · Score: 1

    Yes... That is what a Coincidence is. When 2 things that seem to have a connection while they don't

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  30. Real-Time, too! by delphi125 · · Score: 2, Funny

    As Roger Needham quipped, Multics was design for the real-time processes of geological processes.

    1. Re:Real-Time, too! by Anonymous Coward · · Score: 0

      I had to use Multics at the US Geological Survey. If you include the time to create the software, it was slower than geological processes. One of the best days of my life was when I learned ISD (Information Systems Division) finally accepted how much everyone hated it and dumped it. Rumor had it, they gave it to Iran.

  31. The Michigan Terminal System... by John+Hasler · · Score: 1

    ...came first.

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  32. I was a Multics user and code developer by nani+popoki · · Score: 4, Interesting
    in the 1970s. I programmed in PL/1. While the language was complex (being a synthesis of the most difficult-to-implement features from FORTRAN, COBOL and Algol), it certainly was a fine development environment *on Multics*.

    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.

    1. Re:I was a Multics user and code developer by abigor · · Score: 1

      People like you really need to post here more often.

    2. Re:I was a Multics user and code developer by Anonymous Coward · · Score: 0

      Discarding Lisp to use C++, Java and Python? Madness. Do you also throw out tactical nukes to use arrows, muskets and machine guns?

    3. Re:I was a Multics user and code developer by Anonymous Coward · · Score: 0

      But we need to fight with compatible tools to have access to the vast pool of mercenaries!

    4. Re:I was a Multics user and code developer by nani+popoki · · Score: 1

      It's more like "we need to fight with compatible tools in order to be employed as a mercenary" -- I freely admit that I program in the languages I do simply because that's where most of the jobs are. At 61, I have no intention of changing careers or retiring; I still like to code and I can still make a living doing it.

    5. Re:I was a Multics user and code developer by Skjellifetti · · Score: 1

      My first CS course in my freshman year (1977) was "Structured Programming in PL/I. The only thing I really remember was that the following was legal:

      IF IF = THEN THEN THEN = ELSE; ELSE ELSE = IF;

    6. Re:I was a Multics user and code developer by ZosX · · Score: 1

      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....

  33. x86 segmentation and Multics by yuhong · · Score: 1

    Don't forget the segmentation that was introduced with the 286's protected mode was influenced by Multics as well.

    1. Re:x86 segmentation and Multics by Anne+Thwacks · · Score: 1

      The 286 memory management was a direct ripoff of the PDP11/70's. No direct Multics influence whatever.

      --
      Sent from my ASR33 using ASCII
  34. Re:Um, wasn't bloated Multics the reason *WHY* . . by Abreu · · Score: 3, 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...

    --
    No sig for the moment.
  35. Re:Um, wasn't bloated Multics the reason *WHY* . . by gv250 · · Score: 1

    "horse manure was the catalyst for the automobile"

    Just because it couldn't be more off-topic, The Horse & the Urban Environment describes this relationship quite well.

  36. Re:Um, wasn't bloated Multics the reason *WHY* . . by Anonymous Coward · · Score: 0

    Stop arguing with myself!

  37. Re:Um, wasn't bloated Multics the reason *WHY* . . by vlm · · Score: 3, 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?

    --
    "Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
  38. Multics, comp.risks, and NSA by cpm99352 · · Score: 1

    I'm surprised to see the lack of comp.risks here in the comments. Multics was a phenomenally well designed OS from a security perspective. So much so that NSA recruiters at college took an interest in you if you had Multics experience...

  39. Memories and Friends by Anonymous Coward · · Score: 0

    I was first introduced to Multics in 1984 as a freshman at the University of Southwestern Louisiana (now University of Louisiana at Lafayette). I was lucky, I had a PC (a Kaypro 4) and a fancy new 1200 baud modem for dialing into the system. So I didn't have to wait in line in the terminal room for seat at one of the TVI terminals. With only experience with CP/M, Multics was a real eye-opener. It was an awesome system and had many features that I still miss today.

    While there I was privledged to know a fine Multician, James Dugal. His name is sprinkled throughout Multics lore. I was proud to call him friend. He is missed.

    Johnie Stafford

  40. Not limited to computing... by interploy · · 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.

    1. Re:Not limited to computing... by Tablizer · · Score: 1

      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.

      And that's where Microsoft excels: knowing just how much to squeeze you and when. Gates was a gifted poker player, after all.
           

  41. I think this is irony, but I'll still share... by stakovahflow · · Score: 1
    --
    Holy happy hippy crap!
  42. Re:Um, wasn't bloated Multics the reason *WHY* . . by LWATCDR · · Score: 1

    Hey whats wrong with getting a trophy OS. You know an OS can never be too thin or too new :)

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  43. Antithesis by Dynamoo · · Score: 1
    In some ways, Unix is very like Multics. In some other ways, Unix is the complete Antithesis of Multics. Unix copied some of what was good, left out most of what was bad, and left some of the really cool features to be forgotten. In other words, Multics made Unix the shape it is.. and that of course influenced everything down through Linux, Mach, the iPhone, Android etc etc.

    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 processor with others!

    --
    Never email donotemail@WeAreSpammers.com
  44. Re:Um, wasn't bloated Multics the reason *WHY* . . by spitzak · · Score: 1

    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.

  45. Domo Arigato by Anonymous Coward · · Score: 0

    Dr. Corbato

  46. +1 funny by Anonymous Coward · · Score: 0

    nt

  47. Re:Um, wasn't bloated Multics the reason *WHY* . . by Anonymous Coward · · Score: 0

    Man, you just solved the fuel crisis.

  48. Stupid Comment by omb · · Score: 3, Interesting

    Corbato designed and taught the Architecture that underpinned the UNIX developers and Martin Richards (of Cambridge UK) later, in 1970, brought BCPL, evolving into B, C, ... (_but_ definitely not C++)

    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

    1. Re:Stupid Comment by Have+Brain+Will+Rent · · Score: 1

      The guys you mention certainly deserve respect, however I hate to break it to you but there was already a healthy computer industry and it would have continued growing with or without those guys. For just one example from the period there is DEC minicomputers, which were cheap and small compared to the mainframes of the day, had a huge effect on increasing the spread of computers and introducing their use to laboratories. And IBM had TSO for timesharing. IBM also introduced APL, the first interactive language for serious mathematical programming (as opposed to basic which was intended for teaching). No, the industry might have evolved differently but it would have evolved and grown just the same.

      --
      The tyrant will always find a pretext for his tyranny - Aesop
    2. Re:Stupid Comment by omb · · Score: 1

      You don't need to break anything, you are just displaying your manifest ignorance, complete manifest ignorance.

      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 "Snake Oil"

      The 360/30, Announced April 7, 1964 and withdrawn June 22, 1970, was IBM first 360 model but was more like a 1401, and not till the 360/67, the first VM machine, was the line viable time sharing machine, for which TSO was developed as a shell on to of OS360. The PDP8 and PDP8S were built by Digital Equipment Corporation (DEC) between 1965 and 1990, with the 8S as the first viable lab machine (the PDP4, 5, 6, & 7 were all very low volume) The PDP8/9/10/15/11/VAX were all serious machines and DEC's huge mistake was to abandon the PDP10, for VAX and not to understand the role of UNIX. Gordon Bell was am major Architect and lead architect for the VAX

      So, basically all your history and analysis is wrong, STFU.

    3. Re:Stupid Comment by Have+Brain+Will+Rent · · Score: 1
      Nothing you've said in any way refutes what I said nor does it support the claim that I was responding to - that there would be no computer industry without the guys you mention.

      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 oil."

      Oh and the connection between Ken Olsen and "Snake Oil" was his reference to, in his opinion, certain vendors of Unix systems presenting Unix as a panacea - that promoting this attitude was like selling snake oil. That was in the 80's long after the era under discussion.

      As for IBM - I was running APL on, iirc, a 360/50 and I can tell you that was effective time-sharing and it did not require VM. There was also CAI running off the same machine driving dozens of interactive terminals on campus.

      And let's not forget the contributions of other companies like Univac. Oh and Burroughs who introduced the stack architecture in its 1961 B5000 - gee I wonder if anybody is still using machines with stacks? The B5000 was recognized as being far ahead of its time. And at the same time they introduced the use of Algol as the main language of the system - a language that was arguably superior to any other of the time.

      Oh and speaking of Algol it was widely used in industry and academia for decades as the standard for describing algorithms and is the original source of many concepts still found in modern languages. The Burroughs version was done by Hoare, Dijkstra and others - you might have heard of them. Or perhaps Naur, Backus, Knuth, Wirth and a host of others you left out when deciding we couldn't have a computer industry with the handful you mention.

      Oh and you talk about BCPL, B etc. leading to C. Well CPL (of which BCPL was a stripped down version), Simula (Algol+Classes), Pascal, Scheme and Ada were all Algol influenced languages. BNF was a direct result of the development work on ALGOL.

      And if you think the military wouldn't have driven the creation of a computer industry all by itself you are mistaken.

      There's so much more... but that's all the time I'm gonna spend on you.

      Lastly, as for your "stfu" ... good god how old are you? Twelve? Your idolisation of some people, apparent ignorance of others and attempts at sweeping prognostication based on nothing is just juvenile. Please, grow up.

      --
      The tyrant will always find a pretext for his tyranny - Aesop
  49. Re:Um, wasn't bloated Multics the reason *WHY* . . by Darinbob · · Score: 2, Insightful

    Linux and BSD are positively bloated compared to the first Unix systems. It first ran on a computer with only 64K after all. Unix wouldn't have survived if it had stuck to the first few versions, it would be far too limiting. What made it succeed, as opposed to its contemporaries, was that it was relatively portable and could migrate to better computers when they came along, and it was relatively open (for the time) so that others could grow and adapt it.

  50. Re:I wish it never died! Revisited by omb · · Score: 1

    TECO is fine, and VIM is almost as good if you know, and enable Perl.

    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 earlier Balmer style
    interoperability Canute!

  51. Re:Um, wasn't bloated Multics the reason *WHY* . . by Max+Littlemore · · Score: 1

    "MS-DOS was the catalyst for Linux"

    Come on, MS-DOS was the best operating system MicroSoft ever produced!

    --
    I don't therefore I'm not.
  52. Re:Um, wasn't bloated Multics the reason *WHY* . . by ogdenk · · Score: 2, 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.

  53. Re:Um, wasn't bloated Multics the reason *WHY* . . by lennier · · Score: 2, 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 merits, but because it's dragged a social and aftermarket ecosystem (often one designed purely to patch its flaws) up with it.

    Case in point: virtualization. In the 1970s, IBM mainframes had VM. The PCs laughed at the mainframes and slowly took over. Now, we're reinventing all that mainframe virtualization tech... and putting it over the top of Windows, which is still DOS- and 80x86 compatible. Meanwhile, even the IBM 360 had invented fully virtualized, hardware-independent instruction sets... but in the bold new Wintel data centre world, we have emulated x86, an instruction set not at all designed for portability.

    It was probably IBM's fault for being so tightly protective of their IP and not realising that they could possibly be out-competed by the descendants of the micros - but we haven't necessarily ended up with a better solution, in the long run, by reinventing the mainframe the long and hard and clumsy way.

    --
    You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
  54. GE-645 by Anonymous Coward · · Score: 0

    I was in the used computer business in the early 70s and bought the 645 that was at Bell Labs. still have a bunch of circuit boards from it
    I will be putting them up for sale soon....
    Bill

  55. cool story by bluethundr · · Score: 1

    cool story, bro. full of WIN!!! but /. needs to be moar facebookable these days. images don't show up anymore when posting linkages... :-(((

    --
    Quod scripsi, scripsi.
  56. Re:Um, wasn't bloated Multics the reason *WHY* . . by Have+Brain+Will+Rent · · Score: 1

    It would run in less than 64KB. I had it running on a 28KW (16 bit) machine. It is also worth pointing out that at the same time DEC had an operating system for Real-Time computing and one for timesharing - both running in 28KW on PDP-11's and there was TOPS-10 running on the PDP-10 with 256K.

    --
    The tyrant will always find a pretext for his tyranny - Aesop
  57. Re:Um, wasn't bloated Multics the reason *WHY* . . by lena_10326 · · Score: 1

    Come on, MS-DOS was the best operating system MicroSoft never produced!

    Mini-meme alert: There fixed that for you. QDOS

    --
    Camping on quad since 1996.
  58. Multics the OS we loved to hate by Anonymous Coward · · Score: 0

    I used Multics in the eary 80s at the INRIA, it was incredibly slow... awfully complex, the documentation took severall large cabinets..
    And compared to the Onyx (an early Z8000 based Unix machine) "unexiting"...

    But I confess a strong nostalgy second only to "ernie covax" (4.0/4.1 Bsd) for the system, the greenberg emacs implementation was an work of art and using algol 68 an experience in alternate reality...

    And looking backward, is was a "small" operating system "only 1,5 million lines" of PL/1 and 400K lines of assembly code" (vs about 40K for Unix V7) (of course this was before X11, wysiwyg editing etc...

        Here is to you Multics, cheers !

  59. Re:Um, wasn't bloated Multics the reason *WHY* . . by Max+Littlemore · · Score: 1

    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.

    And still the best operating system MicroSoft ever produced!

    --
    I don't therefore I'm not.
  60. Re:Um, wasn't bloated Multics the reason *WHY* . . by chthon · · Score: 1

    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.