From: clemc@ccc.com (Clem cole)
Subject: [TUHS] PDP-11 questions
Date: Sun, 24 Jan 2016 21:14:43 -0500 [thread overview]
Message-ID: <22770A9B-7F5D-4FE4-8667-78D326239901@ccc.com> (raw)
In-Reply-To: <A0FA0A32-A363-44B2-AE79-D116C39B1A9A@yahoo.com>
UNIX was cheap (free with a$100 tape coping fee) but processors were not as discounted as much as you might think. Yes there was a university price sheet but DEC was still making 45% gross margins on them. And DEC was no different than its competitors
Sent from my iPhone
> On Jan 24, 2016, at 8:55 PM, David Ritchie <deritchie at yahoo.com> wrote:
>
> But wasn't a big part of the reason that DEC was successful in academia that PDP's were pretty heavily discounted vs. commercial pricing for similar compute power? Likewise with pricing for Unix?
>
> David Ritchie
>
> Sent from my iPhone
>
>> On Jan 24, 2016, at 17:40, Norman Wilson <norman at oclsc.org> wrote:
>>
>> Noel Chiappa:
>>
>> I'd lay good money that the vast majority of PDP-11's never ran Unix. And
>> UNIX might have happened on some other machine - it's not crucially tied to
>> the PDP-11 - in fact, the ease with which it could be used on other machines
>> was a huge part of its eventual success.
>>
>> =======
>>
>> I have to disagree in part: the PDP-11 is a big part of
>> what made UNIX so widespread, especially in university
>> departments, in the latter part of the 1970s.
>>
>> That wasn't due so much to the PDP-11's technical details
>> as to its pricing. The PDP-11 was a big sales success
>> because it was such a powerful machine, with a price that
>> individual departments could afford. Without a platform
>> like that, I don't think UNIX would have spread nearly the
>> way it did, even before it began to appear in a significant
>> way on other architectures. Save for the VAX, which was
>> really a PDP-11 in a gorilla suit, that didn't really happen
>> until the early 1980s anyway, and I'm not convinced it
>> would have happened had UNIX not already spread so much
>> on the PDP-11.
>>
>> It worked both ways, of course. I too suspect that a
>> majority (though I'm not so sure about `vast') of PDP-11s
>> never ran UNIX. But I also suspect that a vast majority
>> of those that did might not have been purchased without
>> UNIX as a magnet. I don't think those who weren't
>> around in the latter 1970s and early 1980s can appreciate
>> the ways in which UNIX captured many programmers and
>> sysadmins (the two were not so distinct back then!) as
>> no other competing system could. It felt enormously
>> more efficient and more pleasant to work on and with
>> UNIX than with any of the competition, whether from DEC
>> or elsewhere. At the very least, none of the other
>> system vendors had anything to match UNIX; and by the
>> same token, had UNIX not been there, other hardware
>> vendors' systems would have had better sales.
>>
>> Sometime around 1981, the university department I worked
>> at, which already had a VAX-11/780 and a PDP-11/45 running
>> UNIX, wanted to get another system. Data General tried
>> very hard to convince us to buy their VAX-competitor.
>> I remember our visiting their local office to run some
>> FORTRAN benchmarks. The code needed some tweaking to
>> work under their OS, which DG claimed was better than
>> UNIX. Us UNIX people had trouble restraining our chuckles
>> as we watched the DG guys, who I truly believe were experts
>> in their own OS, taking 15 or 20 minutes to do things that
>> would have taken two or three with a few shell loops and
>> ed commands.
>>
>> DG did not get the sale. We bought a second-hand VAX.
>> Blame UNIX.
>>
>> Norman Wilson
>> Toronto ON
next prev parent reply other threads:[~2016-01-25 2:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 22:40 Norman Wilson
2016-01-25 1:55 ` David Ritchie
2016-01-25 1:59 ` Ronald Natalie
2016-01-25 2:14 ` Clem cole [this message]
2016-01-25 11:29 ` Tony Finch
2016-01-25 13:25 ` Ronald Natalie
2016-01-25 16:18 ` Pete Turnbull
2016-01-25 19:37 ` Clem Cole
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 20:07 Doug McIlroy
2016-01-26 20:44 ` Clem Cole
2016-01-26 19:36 Doug McIlroy
2016-01-26 19:59 ` Warren Toomey
[not found] <mailman.29.1453684304.15972.tuhs@minnie.tuhs.org>
2016-01-25 3:07 ` Johnny Billquist
2016-01-25 3:09 ` Johnny Billquist
2016-01-25 12:54 ` John Cowan
2016-01-25 13:09 ` Johnny Billquist
2016-01-25 13:49 ` Johnny Billquist
2016-01-25 16:00 ` John Cowan
2016-01-25 16:17 ` Johnny Billquist
2016-01-25 16:43 ` John Cowan
2016-01-25 1:11 Noel Chiappa
2016-01-25 1:30 ` Clem cole
2016-01-24 22:40 Norman Wilson
2016-01-25 0:23 ` Ronald Natalie
2016-01-24 18:56 Noel Chiappa
[not found] <mailman.25.1453658502.15972.tuhs@minnie.tuhs.org>
2016-01-24 18:34 ` Johnny Billquist
2016-01-24 18:30 Noel Chiappa
2016-01-24 18:36 ` Ronald Natalie
2016-01-24 21:10 ` John Cowan
2016-01-25 0:11 ` scj
2016-01-25 0:36 ` Clem cole
2016-01-24 18:01 Noel Chiappa
2016-01-24 17:37 Mark Longridge
2016-01-24 18:49 ` Clem Cole
2016-01-25 3:16 ` Dave Horsfall
2016-01-25 5:32 ` Warren Toomey
2016-01-25 12:27 ` Clem cole
2016-01-25 13:38 ` Lawrence Stewart
2016-01-25 14:15 ` Clem Cole
2016-01-26 19:52 ` Dave Horsfall
2016-01-26 20:41 ` 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=22770A9B-7F5D-4FE4-8667-78D326239901@ccc.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).