The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: <tuhs@minnie.tuhs.org>, Al Kossow <aek@bitsavers.org>
Subject: Re: [TUHS] a possible source for 4.1BSD tapes
Date: Mon, 11 Mar 2019 05:46:38 +0000	[thread overview]
Message-ID: <ADFDF14544A65F35.9f917bb9-1555-42a4-a4b7-828cb9d3df0b@mail.outlook.com> (raw)
In-Reply-To: <de2eb3ea-a074-96bc-4910-91119f2c7e74@bitsavers.org>

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

I'm not blaming anyone, as a matter of fact I'm super grateful for all the hard work that is done to preserve what is there on these old tapes, but it's super frustrating that we don't have good historical artifacts.  And that tapes are so seemingly useless. 




I'm 100% out of my element, but is there a kyrolux like device for tapes?  It seems so many 'cut short' and yet I image there is most certainly more tape on the spool. 




I'm just a n00b, and apologize if it's a dumb thing to ask. 




I linked to the bitsaver stuff when writing on the 4.1 stuff as they booted in simh and gave a seemingly working system, but clearly they are missing stuff. I guess I need to figure out the sccs and how to find the latest date on a tape and work from that date based on the CD archive. 




But thanks again, Al for your bits that has me hooked on looking at the latest digital artifacts!! 




I still have hope that more of TripOS eventually surfaces 






On Mon, Mar 11, 2019 at 8:26 AM +0800, "Al Kossow" <aek@bitsavers.org> wrote:












On 3/10/19 3:53 PM, Mike Haertel wrote:
> Warner Losh writes:
>> There's also
>> http://bitsavers.trailing-edge.com/bits/BSD/BSD4.1_bootable.tap.gz which I
>> just noticed...

Likely a Memorex sticky tape that stripped its oxide when I tried to read it.

These were read a long time before I had a tape oven.

I've not dug back into what I still have from the 4BSD days, or in the CHM
archives since I thought Kirk had this all covered.








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

  parent reply	other threads:[~2019-03-11  5:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10  7:31 Mike Haertel
2019-03-09 23:24 ` Nigel Williams
2019-03-10 11:18   ` Lars Brinkhoff
2019-03-10 20:55     ` Warner Losh
2019-03-10 22:53       ` Mike Haertel
2019-03-11  0:25         ` Al Kossow
2019-03-11  1:15           ` Mike Haertel
2019-03-11  5:46           ` Jason Stevens [this message]
2019-03-11 17:28             ` Mike Haertel
2019-03-11 17:38               ` Larry McVoy
2019-03-11 18:33                 ` Lars Brinkhoff
2019-03-11 18:41                 ` Clem Cole
2019-03-12  6:21                 ` Nigel Williams
2019-03-12  6:32                   ` Jason Stevens
2019-03-12 12:44                 ` arnold
2019-03-11 21:47             ` Al Kossow
2019-03-23 17:50         ` reed
2019-03-24  4:19           ` Lars Brinkhoff
2019-03-10  8:20 ` arnold
2019-03-10 15:50   ` Mike Haertel
2019-03-10 19:54     ` arnold
2019-03-10 20:33       ` Warner Losh
2019-03-25 17:19 Richard Tobin

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=ADFDF14544A65F35.9f917bb9-1555-42a4-a4b7-828cb9d3df0b@mail.outlook.com \
    --to=jsteve@superglobalmegacorp.com \
    --cc=aek@bitsavers.org \
    --cc=tuhs@minnie.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).