The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: alan@alanlee.org
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Current Ownership of 3B/WECo Computer IPs
Date: Sun, 10 Sep 2023 22:02:55 -0400	[thread overview]
Message-ID: <689bc9fc3e5cc8d6772b98f12b96ba92@alanlee.org> (raw)
In-Reply-To: <2884e81581b595ec2c4fc11fc6b2a8ab@alanlee.org>

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]



Let me clarify.  A few of us have reached out to various people about 
both 3B2 and WE32k information.  The main response them has been it's 
still in-use to varying degrees by customers.  I assume through 
emulation to keep legacy systems running.  And they cannot release any 
details.

The two people that would know the most about the status of that IP is 
William Caughlin [1] at the AT&T Archives and Ed Eckert - Archivist at 
Nokia Bell Labs.

-Alan

On 2023-09-10 21:35, alan@alanlee.org wrote:

> My understanding is all the WE IP was retained through the 
> Alcatel-Lucent mergers and is now owned by Nokia.  That would include 
> all the 3Bx systems and WE32k.
> 
> -A


Links:
------
[1] https://www.linkedin.com/in/william-caughlin-59571546/

[-- Attachment #2: Type: text/html, Size: 1245 bytes --]

  reply	other threads:[~2023-09-11  2:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11  1:11 [TUHS] " segaloco via TUHS
2023-09-11  1:35 ` [TUHS] " alan
2023-09-11  2:02   ` alan [this message]
2023-09-11  3:17   ` Kevin Bowling
2023-09-11  1:43 ` Clem Cole
2023-09-11  2:57   ` segaloco via TUHS
2023-09-11  3:37     ` Clem Cole
2023-09-11 15:34       ` Paul Winalski
2023-09-11 17:46         ` [TUHS] nassau smelting was " Mark Seiden
2023-09-11 19:58           ` [TUHS] " Douglas McIlroy
     [not found]             ` <F227DB6D-F1D5-45CD-9F7A-906732892105@seiden.com>
2023-09-11 21:06               ` Douglas McIlroy

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=689bc9fc3e5cc8d6772b98f12b96ba92@alanlee.org \
    --to=alan@alanlee.org \
    --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).