The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Corbato dead
Date: Mon, 8 May 2023 10:18:47 -0400	[thread overview]
Message-ID: <CAKH6PiXVMeCt8LOmAiYAfGpstJzwED=XvDhC2v+gJQVdkKSqpA@mail.gmail.com> (raw)

Although it dates from four years ago, MIT's obituary for Corbató was
still interesting to reread. It couldn't bring itself to mention
Unix--only the latecomer Linux. It also peddled some mythology about
Whirlwind from the decade before timesharing.

"Whirlwind was ... a rather clunky machine. Researchers often had
trouble getting much work done on it, since they had to take turns
using it for half-hour chunks of time. (Corbató said that it had a
habit of crashing every 20 minutes or so.)"

"Clunky" perhaps refers to Whirlwind's physical size. It occupied two
stories of the Barta Building, not counting the rotating AC/DC
motor-generators in the basement. But it was not ponderous; its clean
architecture prefigured "RISC" by two decades.

Only a few favored people got "chunks" of (night) time on Whirlwind
for interactive use. In normal business hours it was run by dedicated
operators, who fed it user-submitted code on punched paper tape.
Turnaround time was often as short as an hour--including the
development of microfilm, the main output medium. Hardware crashes
were rare--much rarer than experience with vacuum-tube radios would
lead one to expect--thanks to "marginal testing", in which voltages
were ramped up and down once a day to smoke out failing tubes before
they could affect real computing. My recollection is that crashes
happened on a time scale of days, not minutes.

"Clunky" would better describe the interface of the IBM 704, which
displaced Whirlwind in about 1956. How backward the 60-year-old
uppercase-only Hollerith card technology seemed, after the humane full
Flexowriter font we had enjoyed on Whirlwind. But the 704 had the
enormous advantages of native floating-point (almost all computing was
floating-point in those days) and FORTRAN. (Damn those capital
letters!)

Doug

             reply	other threads:[~2023-05-08 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 14:18 Douglas McIlroy [this message]
2023-05-08 16:11 ` ron minnich
2023-05-08 18:46   ` Clem Cole
2023-05-08 22:06     ` Rich Salz
2023-05-08 22:11       ` Jon Steinhart
2023-05-09  4:53       ` ron minnich
2023-05-09  8:41         ` Jaap Akkerhuis
  -- strict thread matches above, loose matches on Subject: below --
2023-05-04 21:59 [TUHS] " Rich Salz
2023-05-04 22:41 ` [TUHS] " Rich Salz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKH6PiXVMeCt8LOmAiYAfGpstJzwED=XvDhC2v+gJQVdkKSqpA@mail.gmail.com' \
    --to=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).