The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mary Ann Horton <mah@mhorton.net>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Likelihood of Extant Less-Distributed Tapes and Sources
Date: Tue, 9 Aug 2022 14:09:32 -0700	[thread overview]
Message-ID: <99f89c2a-5b62-c8fc-825e-edb8ff7b458e@mhorton.net> (raw)
In-Reply-To: <xono7wtqwg7.fsf@anduin.eldar.org>

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

I'm sure CB-UNIX was developed at CB, e.g. 6200 E Broad, by Dale 
DeJager's and Tom Cook's team, the Operating Systems Group (cbosg).

As Brad aptly describes, there is no hope of finding any old tapes in 
the CB building. It's been part of Mt. Carmel hospital for years.

Thanks,

/Mary Ann Horton/ (she/her/ma'am)
maryannhorton.com <https://maryannhorton.com>

On 8/9/22 08:16, Brad Spencer wrote:
> segaloco via TUHS<tuhs@tuhs.org>  writes:
>
>> Good morning everyone.  Wanted to pose the question since folks here would probably be more likely to know than anyone.
>>
>> What are the chances that there are surviving tapes of some of the UNIX versions that weren't so well publicized.  The versions that come to mind are the CB and USG lines especially, with PWB 2.0 and TS 4.0 getting honorable mention.  If folks will recall, we did luck out in that Arnold, a member of this mailing list, did have a documentation trove from TS 4.0, but no binary or source code assets.  This had me curious on what trying to unearth these would even look like.
>>
>> Has anyone tried to dive deep on this sort of stuff before?  Would it look more like trying to find old Bell facilities that might have a tape bumping around in a box in a basement somewhere, or is it more likely that if anything survived it would have been due to being nabbed by an employee or contractor before disposal?  Or even just in general, what would folks say is the likelihood that there is a recoverable tape of any of this material just waiting to see the light of day?  The closest we have on CB is a paper scan of the kernel sources, and I don't know that any assets from USG-proper have ever percolated up, closest thing to any of that would be the kernel routine description bumping around on the archive somewhere.  PWB 2.0 is mentioned in several places, but no empirical evidence has surfaced as far as I know, and with 4.0 of course we have the documents Arnold thankfully preserved, but that's it.
> [snip]
>
> I am not sure where CBUNIX was actually developed, but I spent 12 years
> at 6200 Broad Street and a tiny bit at 6400 Broad Street and knew folks
> who were associated with the Dublin Training center.  I didn't do
> operating systems development and I did not work on the physical switch
> gear, rather I was in one of the many support system products that got
> sold to all of the RBOCs and around the world.
>
> The Broad Street site(s) have been sold off many years ago.  All that
> remains of 6200 Broad is the front part of the building.  The back part,
> the factory and much of the high bay area, fell in on itself some years
> ago and the rubble was cleared away.  The concrete floor still remains.
> A hospital system bought the building grounds and much of the rest of
> the land was sold off and houses were built and some fast food joints
> put in.  As far as I can tell 6400 Broad is gone, having been torn down
> some time ago.
>
> My memory isn't clear what happened to Dublin, but around the time of
> the Lucent split from AT&T or perhaps during the dark down years that
> followed, Dublin ceased to be a thing.  I suspect sold a long time ago.
>
> I would guess that if there is anything left of CBUNIX it would be in a
> personal collection of stuff at this point.
>
> The story of the sale of 6200 is a bit of a mess...  the hospital system
> actually bought the front part some years before Lucent left the
> building completely (Lucent moved their entrance to the east side of the
> building).  I had an office in the front part of the building and we had
> a rush move to cubes that were created in the high bay area in the
> middle of the building when the sale was done and over with.  Lots and
> lots of computers and devices were destroyed during that time as there
> was no space to keep them and I am sure that a lot was lost.  The 6200
> site had a industrial sized metal compactor and it was not uncommon for
> entire 3B2, Sun workstations and probably entire Vax systems would just
> be tossed in and smashed (flattened, crushed and shredded).  Our group
> had a 3B system that was used for simulation work to the product I
> worked on and it was marked for destruction by mistake and destroyed out
> from under us one day.
>
>
>

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

      reply	other threads:[~2022-08-09 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 19:08 [TUHS] " segaloco via TUHS
2022-08-09 15:16 ` [TUHS] " Brad Spencer
2022-08-09 21:09   ` Mary Ann Horton [this message]

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=99f89c2a-5b62-c8fc-825e-edb8ff7b458e@mhorton.net \
    --to=mah@mhorton.net \
    --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).