From: segaloco via TUHS <tuhs@tuhs.org>
To: Warner Losh <imp@bsdimp.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: 3B21D
Date: Thu, 04 Jul 2024 20:22:05 +0000 [thread overview]
Message-ID: <xs_YVRH04ph-wc8ou4UTy2pu3fMit0_cgDpbjb5LyldYv5mqHciknZAsMAu08-tvECVJW_iLDL_Wq0XFBIRzdTYobtvzptFISZPUb8sPX3c=@protonmail.com> (raw)
In-Reply-To: <CANCZdfoRR7HjN46ZKGRG=V1+YX=-8NFhtVkvTQE+3BLZfdJPEA@mail.gmail.com>
On Thursday, July 4th, 2024 at 1:14 PM, Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Thu, Jul 4, 2024, 2:02 PM Kevin Bowling <kevin.bowling@kev009.com> wrote:
>
> > Howdy,
> >
> > I now have this pictured 3B21D in my facility
> > http://kev009.com/wp/2024/07/Lucent-5ESS-Rescue/
> >
> > It will be a moment before I can start work on documentation of the
> > 3B21D and DMERT/UNIX-RTR but wanted to share the news.
>
>
> Awesome accomplished. Can't wait to see the outcome.
>
> Warner
>
>
>
> > Regards,
> > Kevin
Kudos, I'm quite envious, this is awesome news! I appreciate your writeup, touching on the odd world this lives in, between computer and telecom appliance. Whether the 3B20 family was liked out in the general computing world or not, the impact on telecommunications is clear with the long shadow of the 5ESS family of switches.
Hopefully Lucent was still keen on providing /usr/src and /usr/man :)
I'm still holding out hope a WECo-era machine pops up someday...but either way, glad to finally see something in this lineage in the hands of someone with a keen eye for UNIX and Bell System history!
- Matt G.
next prev parent reply other threads:[~2024-07-04 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 20:02 [TUHS] 3B21D Kevin Bowling
2024-07-04 20:14 ` [TUHS] 3B21D Warner Losh
2024-07-04 20:22 ` segaloco via TUHS [this message]
2024-07-06 17:50 ` Kevin Bowling
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='xs_YVRH04ph-wc8ou4UTy2pu3fMit0_cgDpbjb5LyldYv5mqHciknZAsMAu08-tvECVJW_iLDL_Wq0XFBIRzdTYobtvzptFISZPUb8sPX3c=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=imp@bsdimp.com \
--cc=segaloco@protonmail.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).