The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: beebe@math.utah.edu (Nelson H. F. Beebe)
Subject: [TUHS] [TUHS} PDP-11, Unix, octal?
Date: Wed, 18 Jan 2017 07:28:36 -0700	[thread overview]
Message-ID: <CMM.0.96.0.1484749716.beebe@gamma.math.utah.edu> (raw)

On the subject of the PDP-10, I recall seeing people at a DECUS
meeting in the early 1980s wearing T-shirts that proclaimed

	I don't care what they say, 36 bits are here to say!

I also recall a funny advertizing video spoof at that meeting that
ended with the line

	At DIGITAL, we're building yesterday's tomorrow, today.

That meeting was about the time of the cancellation of the Jupiter
project at DEC that was planned to produce a substantially more
powerful follow-on to the KL-10 processor model of the PDP-10 (we had
two such at the UofUtah), disappointing most of its PDP-10 customers.

Some of the Jupiter technology was transferred to later VAX models,
but DEC never produced anything faster than the KL-10 in the 36-bit
line.  However, with microcomputers entering the market, and early
workstations from Apollo, LMI, Sun, and others, the economics of
computing changed dramatically, and departmental mainframes ceased to
be cost effective.

Besides our mainframe DEC-20/60 TOPS-20 system in the College of
Science, we also ran Wollongong BSD Unix on a VAX 750, and DEC VMS on
VAX 780 and 8600 models.  In 1987, we bought our first dozen Sun
workstations (and for far less than the cost of a DEC-20/60).

After 12 good years of service (and a forklift upgrade from a 20/40 to
a 20/60), our KL-10 was retired on 31-Oct-1990, and the VAX 8600 in
July 1991.  Our productivity increased significantly in the Unix
world.

I wrote about memories and history and impact of the PDP-10 in two
keynote addresses at TUG meetings in articles and slides available at

	http://www.math.utah.edu/~beebe/talks/2003/tug2003/
	http://www.math.utah.edu/~beebe/talks/2005/pt2005/

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe at math.utah.edu  -
- 155 S 1400 E RM 233                       beebe at acm.org  beebe at computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe/ -
-------------------------------------------------------------------------------


             reply	other threads:[~2017-01-18 14:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 14:28 Nelson H. F. Beebe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-18  2:33 Noel Chiappa
2017-01-18  3:06 ` Steve Johnson
2017-01-18  3:36   ` Dan Cross
2017-01-18  6:53     ` Angelo Papenhoff
2017-01-18  7:31       ` ron minnich
2017-01-18  8:09         ` Angelo Papenhoff
2017-01-18 21:04     ` Steve Johnson
2017-01-18 21:42       ` Charles Anthony
2017-01-18  6:04   ` Lars Brinkhoff
2017-01-18 18:47     ` Peter Jeremy
2017-01-18 18:58       ` Charles Anthony
2017-01-17  2:23 Doug McIlroy
2017-01-18 16:47 ` Clem Cole

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=CMM.0.96.0.1484749716.beebe@gamma.math.utah.edu \
    --to=beebe@math.utah.edu \
    /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).