From: Kenneth Goodwin <kennethgoodwin56@gmail.com>
To: William Corcoran <wlc@jctaylor.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Reaction to the 3B2 at Bell Labs
Date: Mon, 28 Nov 2022 15:59:50 -0500 [thread overview]
Message-ID: <CAMQbRb3yb5DbuHOMK=c5w8=fj_fZNDCZ7=KWjAYBtBaCc4od4A@mail.gmail.com> (raw)
In-Reply-To: <0EB50C1F-D226-40BF-8F42-43CB988B036E@jctaylor.com>
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
That must be the 300 B superhive model CPU
On Mon, Nov 28, 2022, 1:54 PM William Corcoran <wlc@jctaylor.com> wrote:
> I have a 3b2/300. Anytime you run a command that is compute bound, like
> factoring a large prime number, the CPU buzzes!
>
>
>
> Bill Corcoran
>
>
>
>
>
> On Nov 27, 2022, at 9:52 AM, John P. Linderman <jpl.jpl@gmail.com> wrote:
>
>
>
> [EXTERNAL]
>
>
> We were "gifted" a 3B2, as in "take this and use it!". I ran a "ps"
> command in single user mode, and it took 20 seconds to run.
> Our machine names were themed around bird names, so we christened the 3B2
> "junco". Our director said we had to get along,
> so we renamed it "jay". But everyone knew what the J stood for. The 3B2
> served as a doorstop.
>
> On Sat, Nov 26, 2022 at 11:44 PM Phil Budne <phil@ultimate.com> wrote:
>
>> Larry McVoy wrote:
>> > I read the Wikipedia page on the 9000. It's sad that the 9000
>> > wasn't cancelled when they had better alternatives.
>>
>> In an oral history Bob Supnik described Ken Olsen couldn't get his
>> head around the fact that the NVAX chip could equal the 9000:
>>
>> @2:59:45 in https://www.youtube.com/watch?v=T3tcCBHRIfU
>>
>> In part 2, Bob described how then DEC VP Gordon Bell having earlier
>> predicted when the microprocessor performance curve would cross over
>> minis and mainframes:
>>
>> @1:51:45 in https://www.youtube.com/watch?v=T3tcCBHRIfU
>>
>> He also talks about how the company couldn't command the bsame gross
>> margins as it did in the VAX era.
>>
>
>
> THIS IS AN EXTERNAL EMAIL -- This email was sent from someone OUTSIDE of
> the NSM Insurance Group email system. PLEASE USE CAUTION WHEN REVIEWING
> THIS EMAIL.
>
>
[-- Attachment #2: Type: text/html, Size: 3856 bytes --]
next prev parent reply other threads:[~2022-11-28 21:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 18:46 [TUHS] " Seth Morabito
2022-11-26 19:18 ` [TUHS] " Larry McVoy
2022-11-26 20:04 ` Seth Morabito
2022-11-26 20:42 ` Rob Pike
2022-11-26 21:46 ` Clem Cole
2022-11-26 23:00 ` Marc Donner
2022-11-26 23:23 ` Larry McVoy
2022-11-26 23:47 ` Dan Cross
2022-11-27 0:17 ` Larry McVoy
2022-11-27 4:43 ` Phil Budne
2022-11-27 14:51 ` John P. Linderman
2022-11-27 15:29 ` arnold
2022-11-27 16:11 ` Ron Natalie
2022-11-27 16:59 ` Warner Losh
2022-11-27 18:59 ` arnold
2022-11-27 20:45 ` Rob Pike
2022-11-28 18:53 ` William Corcoran
2022-11-28 20:59 ` Kenneth Goodwin [this message]
2022-11-28 22:33 ` ron minnich
2022-11-28 22:43 ` Marc Donner
2022-11-29 1:49 ` Alan Glasser
2022-12-01 6:10 ` Kevin Bowling
2022-12-01 8:30 ` Andrew Hume
2022-12-01 8:53 ` arnold
2022-12-01 9:19 ` Skip Tavakkolian
2022-12-01 12:25 ` Brad Spencer
2022-12-01 10:00 ` Andrew Hume
2022-12-01 10:17 ` arnold
2022-11-27 14:53 ` Larry McVoy
2022-11-26 19:21 ` Douglas McIlroy
2022-11-29 11:33 ` alan
2022-11-30 2:50 ` Mary Ann Horton
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='CAMQbRb3yb5DbuHOMK=c5w8=fj_fZNDCZ7=KWjAYBtBaCc4od4A@mail.gmail.com' \
--to=kennethgoodwin56@gmail.com \
--cc=tuhs@tuhs.org \
--cc=wlc@jctaylor.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).