From: Warner Losh <imp@bsdimp.com>
To: Ron Natalie <ron@ronnatalie.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Reaction to the 3B2 at Bell Labs
Date: Sun, 27 Nov 2022 09:59:10 -0700 [thread overview]
Message-ID: <CANCZdfrqctPPCv5URKjF1Rt_wYztrdvXEA+ZNP-Y=2ySucM_ag@mail.gmail.com> (raw)
In-Reply-To: <em31cf1b57-00bb-4746-b2ac-4ff34db666af@c62ead55.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Sun, Nov 27, 2022, 9:11 AM Ron Natalie <ron@ronnatalie.com> wrote:
>
> . But everyone knew what the J stood for. The 3B2 served as a doorstop.
>
>
> Shades of the jerq terminal. The J prefix persiste in the code long
> after the nickname was quashed.
>
>
> Being in charge of the Rutgers computer center, we were gifted a lot of
> ATT hardware. We had one 3B20 (now that was a pure piece of phone
> equipment, you shut it down by turning a switch inside and holding the
> button down until it twanged. Just like putting an old 303 modem into
> loop back). We also got three 3B5's (noted for the one installed in the
> New Brunswick computing room that got completely drenched when a pipe burst
> and kept on running) and countless of the 3B2s. I chortled in that
> unless you were logged in as root, you couldn't work the power switch.
> Yanking the cord out of the wall was still and option.
>
When I worked for The Wollongong Group, we had a 3b2, 3b5 and 3b20 for all
the networking products we had. The 3b20 was nice. The 3b5 wasn't
terrible.... the 3b2 was the only machine I've seen that I could visibly
see the characters appear one at a time over the telnet session for some,
but not all, programs. Those programs, iirc, used stdio, but the stdio on
the 3b2 didn't have buffering turned on...
Warner
>
[-- Attachment #2: Type: text/html, Size: 2641 bytes --]
next prev parent reply other threads:[~2022-11-27 17:00 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 [this message]
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
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='CANCZdfrqctPPCv5URKjF1Rt_wYztrdvXEA+ZNP-Y=2ySucM_ag@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=ron@ronnatalie.com \
--cc=tuhs@tuhs.org \
/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).