The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] v7 tape in bitsavers vs recreated tape from Keith Bostic's v7 in TUHS
Date: Mon, 10 Jan 2022 22:11:39 -0600	[thread overview]
Message-ID: <262db701-0f20-9a7b-eb21-73f222ffd2ed@gmail.com> (raw)

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

Today I was looking around for more v7 stuff of interest that I might 
find on the web and came across a tape image in the ATT bits directory: 
http://www.bitsavers.org/bits/ATT/ labeled X7252.2015_UNIX_V7.tap and an 
image of the reel with original and added markings. I downloaded it and 
sure enough, it's a bootable v7. I then compared it with my recreated 
tape image from the files in the Keith Bostic folder on tuhs. The 11.7MB 
tapes are nearly identical, with only a handful of bytes that differ at 
the very end of the tape:

ATT tape:
54532000    000000  000000  024000  000000  000000  000000 000077  000000
54532020    052135  014020  010000  034113  056720  023524 072143  122062
54532040    141401  000000  000000  000000  000000  000000 000000  000000
54532060    000000  000000  000000  000000  000000  000000 000000  000000
54532100    000000  000000  000000  000000  000000  000000 000000  037400
54532120    000000 000000
54532123

Bostic recreated tape:
54532000    000000  000000  024000  000000  000000  000000 177777  177777
54532020

I'm wondering - 1) Does anyone know the provenance of the 
X7252.2015_UNIX_V7.tap 2) Do the bytes at the end of the tapes look 
familiar or particularly meaningful? My knowledge of 40+ y.o. tape 
formats is woefully lacking, but I'm curious.

Will

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

                 reply	other threads:[~2022-01-11  4:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=262db701-0f20-9a7b-eb21-73f222ffd2ed@gmail.com \
    --to=will.senn@gmail.com \
    --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).