The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] PDP-10 in the news today
Date: Tue, 31 Jan 2017 16:33:40 -0500 (EST)	[thread overview]
Message-ID: <20170131213340.65D3A18C0D7@mercury.lcs.mit.edu> (raw)

    > From: Nigel Williams

    > Is it a reasonable claim that the PDP-10 made time-sharing "common"
    > ... I'm presuming that "common" should be read as ubiquitous and
    > accessible
    > I'm wondering if it was really the combination of the PDP-11

Good question; I think a case can be made both ways.

    > (lower-cost more models)

One observation I will make: the two don't have identical time-lines; the
earliest PDP-10 models predate the PDP-11 by a good chunk, and the PDP-11
out-lasted the PDP-10. So that has a big influence, I think, on the question
above.

The first PDP-10 (the KA - we'll leave aside the even earlier PDP-6) was made
out of small cards with individual transistors (B-series Flip Chips), whereas
the earliest PDP-11 model (the -11/20) used SSI TTL on much larger cards.
Ditto on the other end: the last PDP-10 sold used 29xx bit-slice technology,
whereas the PDP-11 lasted through three generations of microprocessor (the
LSI-11, Fonz, and Jaws).

	Noel


             reply	other threads:[~2017-01-31 21:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 21:33 Noel Chiappa [this message]
2017-01-31 23:23 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2017-01-31 21:17 Nelson H. F. Beebe
2017-01-31 13:26 Noel Chiappa
2017-01-31  2:39 Noel Chiappa
2017-01-31  0:56 Nelson H. F. Beebe
2017-01-31  7:41 ` Lars Brinkhoff
2017-01-31  8:12   ` Peter Jeremy
2017-01-31 14:19     ` Clem Cole
2017-01-31 19:33       ` Warren Toomey
2017-01-31 21:07         ` Nigel Williams

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=20170131213340.65D3A18C0D7@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.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).