The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Why did PDPs become so popular?
Date: Wed, 27 Dec 2017 16:51:54 -0500	[thread overview]
Message-ID: <CAC20D2P_N20Z7HZd8j9ffjnvenptqpromDgzJBLi9N13AsBfkQ@mail.gmail.com> (raw)
In-Reply-To: <CAFWeb9JmyAKpxk_14yBT99P2M0kDJB9tRBkRd8MWkcPX5NOULw@mail.gmail.com>

You are mixing a couple of different stories I fear...

If you want the full story get a copy of:   Computer Engineering: A DEC
View of Hardware Systems Design
<https://www.amazon.com/Computer-Engineering-Hardware-Systems-Design/dp/1483207676>

But a snap shot for this mailing list is this ...  The PDP term was used by
KO when he was funding Digital because the VC's the 60s did not believe
that a computer company would succeed.   But making things for the
instrumentation market (Lincoln Labs, Livermore, *etc*.).   This is how
PDP-1 came to be.  The PDP term was keep for the first 25 years (until the
Vax and renaming of the PDP-10/PDP-20 to DECSystem 10/20). [The 1 begat the
6, 9, 15 an 10 families].

The concept of purchasing smaller system, was indeed true.   This was the
idea behind the >>mini-computer<< or *minimal computer* that Gordon Bell
who lad left DEC temporarily to be a CMU Prof for a time began to explore.
 He took the idea and commercialized and the PDP-8 line was the first in
that line.  The 11 & 15 were full computer systems.  DEC also made
something called the PDP-16 'Register Transfer Modules' (RTMs) which was an
attempt to make the small controller idea even more accessible, but the
Intel microprocessor would eclipse them (I think I was the last group at
CMU was talk a course using them.   Another factoid, the predecessor to
VHDL/Verilog and the like, ISPL and ISPS actually spit out 'code' for DEC
RTM modules instead of gates).

But the key point is that in 1975 dollars, a PDP-11/40 system that was good
enough to run something like Sixth Edition of UNIX cost somewhere between
$50k-$150k.   This would have been much, much cheaper than say a PDP-10, or
a equivilent IBM 'mainframe' size system which would have started above $1M.

Clem

On Wed, Dec 27, 2017 at 4:02 PM, Alec Muffett <alec.muffett at gmail.com>
wrote:

> I apologise if this is too far from the main topic, but I wanted to check
> an urban legend.
>
> There is a story - as I have heard it told - that PDPs established their
> place (and popularity) in the marketplace by pointedly *not* advertising
> themselves as "computers", but instead as "programmed data processors".
>
> This was because - so the story goes - that everyone in corporations of
> the time simply *knew* that "computers" came only from IBM, lived in big
> datacentres, had million-dollar price-tags, and required extensive project
> management to purchase; whereas nobody cared enough about a thing called a
> "programmed data processor" to bother bikeshedding the
> few-tens-or-hundreds-of-thousands-of-dollars purchase proposal to an
> inevitable death. Thus, they flitted under the purchasing radar, and sold
> like hotcakes.
>
> I wonder: does this story have substance, please?
>
> Aside from anything else: I draw parallels to the adoption of Linux by
> Wall St, and the subsequent adoption of virtualisation / AWS by business -
> now reflected in companies explaining to ISO27001 auditors that "well, we
> don't actually possess any physical servers..."
>
>     - alec
>
> --
> http://dropsafe.crypticide.com/aboutalecm
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171227/bf04c042/attachment-0001.html>


  parent reply	other threads:[~2017-12-27 21:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-27 21:02 Alec Muffett
2017-12-27 21:50 ` Grant Taylor
2017-12-28  1:23   ` Alec Muffett
2017-12-27 21:51 ` Clem Cole [this message]
2017-12-27 21:52   ` Clem Cole
2017-12-28  2:14   ` Greg 'groggy' Lehey
     [not found] <109152082.5216233.1514413535270.ref@mail.yahoo.com>
2017-12-27 22:25 ` Dave Ritchie
2017-12-27 22:32   ` Dave Horsfall
2017-12-27 23:44     ` Paul Winalski
2017-12-27 23:38   ` Kevin Bowling
2017-12-28  0:07     ` Paul Winalski
2017-12-28  0:45       ` Kevin Bowling
2017-12-28  1:39       ` Ron Natalie
2017-12-28 14:05 Noel Chiappa
2017-12-28 15:59 ` Paul Winalski
2017-12-28 16:08   ` Larry McVoy
2017-12-28 23:28     ` Theodore Ts'o
2017-12-29 11:04       ` Kevin Bowling
2017-12-29 23:35         ` Jon Forrest
2017-12-29 23:58           ` Larry McVoy
2017-12-29 16:38 Larry McVoy
2017-12-29 23:54 ` Kevin Bowling
2017-12-30  0:04   ` Larry McVoy
2017-12-30  0:54   ` Lawrence Stewart
2017-12-30  1:47     ` Kevin Bowling
2017-12-30  2:19       ` Lawrence Stewart
2017-12-30  2:35         ` Paul Winalski
2017-12-30  2:20       ` Paul Winalski
2017-12-31  2:47     ` Henry Bent
2017-12-30  1:07   ` Ron Natalie
2017-12-30  2:30     ` Paul Winalski
2017-12-31  3:00       ` Henry Bent
2017-12-31  9:59         ` Arrigo Triulzi
2017-12-31 15:55         ` Paul Winalski
2017-12-31  5:20 Rudi Blom
2017-12-31 12:56 ` Clement T. Cole
2017-12-31 15:03   ` Steve Simon

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=CAC20D2P_N20Z7HZd8j9ffjnvenptqpromDgzJBLi9N13AsBfkQ@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).