The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Likelihood of Extant Less-Distributed Tapes and Sources
Date: Mon, 08 Aug 2022 19:08:11 +0000	[thread overview]
Message-ID: <i5Qj876R8LbVL1qwr44Mw-rvRK6igQecC92h6ZX0U9ZVQaXZi4m2XXfVnHRpkjcApF45yqWGD99GYGrCWBprdw6kaKkSUh0RF86W9f77NVM=@protonmail.com> (raw)

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.

Thanks in advance for any insight or thoughts.  My concern is that there is a rapidly closing window on ever being able to properly preserve these parts of the UNIX story, although recognition must be paid to all of the hard work folks have done here thus far to keep this valuable part of computing history in the collective consciousness and accessible to researchers and programmers for years and years to come.

- Matt G.

P.S. Even more honorable mention is the Bell Interdata 8/32 work.  I've read several places that never saw outside distribution, but I would have to wonder if any of that work survived beyond the visible portability changes in V7.

             reply	other threads:[~2022-08-08 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 19:08 segaloco via TUHS [this message]
2022-08-09 15:16 ` [TUHS] " Brad Spencer
2022-08-09 21:09   ` 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='i5Qj876R8LbVL1qwr44Mw-rvRK6igQecC92h6ZX0U9ZVQaXZi4m2XXfVnHRpkjcApF45yqWGD99GYGrCWBprdw6kaKkSUh0RF86W9f77NVM=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --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).