The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] PDP-10 in the news today
Date: Tue, 31 Jan 2017 18:23:27 -0500	[thread overview]
Message-ID: <CAC20D2NNsyUirYe+Z835O71yJBPc1aH4Sd3_DXVB84V180wY9Q@mail.gmail.com> (raw)
In-Reply-To: <20170131213340.65D3A18C0D7@mercury.lcs.mit.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]

On Tue, Jan 31, 2017 at 4:33 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:

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

​I agree.
​

>
>
>     > (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
> ​q​
> uestion
> ​ ​
> above.


​Certainly if you include the virtual address extension - aka VAX to the
PDP-11 family - which was birthed in '76.​  Then I would agree the
PDP11/VAX/UNIX combo had case for a larger *footprint*  for making
timesharing "common" from 70-79 -- which is the time period mentioned in
the Wikipedia article.

But I do think to fair to the Wikipedia authors, the 10 and 20 families
during the 1970s were the pretty much the machines that defined the idea of
timesharing to most small colleges and smaller universities until UNIX
takes its stride.

CDC and IBM had a footprint in large and well funded places.  But even in
those schools, the 10/20 was still king in the CS Dept, until UNIX
displaced it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170131/e050c624/attachment-0001.html>


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 21:33 Noel Chiappa
2017-01-31 23:23 ` Clem Cole [this message]
  -- 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=CAC20D2NNsyUirYe+Z835O71yJBPc1aH4Sd3_DXVB84V180wY9Q@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).