The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <>
To: Lars Brinkhoff <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: Extracting files from various old dump/restore tapes
Date: Tue, 23 Aug 2022 07:02:20 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On Mon, Aug 22, 2022 at 11:55 PM Lars Brinkhoff <> wrote:

> Warner Losh wrote:
> > So 60011 is OFS_MAGIC and 60012 is NFS_MAGIC. Both of these are
> > variants on UFS, but really old. And given they are at different
> > offsets, you'll likely need to reverse engineer the offsets used for
> > the platform's dinode.
> So anyway, it seems my best bet would be getting an old "restore" and
> hack it till it runs.
> Part of the problem is that there are hundreds of these images, so it
> would be a lot of work to examine them individually in emulated systems.
> A good first start to examine the content would be to just list the file
> names.

For V7 tapes, you can run the V7 binaries using apout with very little
This is a user-level emulation of a pdp-11 with the system calls for v5,
v6, v7 and
some of the BSDs. It's in the tuhs archives under
I used it to extract files from V7 automatically that I used in the 2.11
script I wrote.

> > Without more specific data it's hard to know if there's an extant
> > binary that can be run in emulation to read these tapes.
> The tapes are from MIT's "Tapes of Tech Square" collection.  Likely
> candidates include PDP-11 V7, 4.x BSD on VAX, and Sun workstations.  I
> suppose the latter would use the big endian format.

Very cool. I suspect if you want one tool for them all, you'll need to take
and teach it to cope with multiple endians and word sizes... It's likely
not a huge
effort, but the restor code from V7 makes use of a lot of type-punning...

> There are also many variations of the tar and cpio formats, but I'm on
> firmer ground there.


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

  reply	other threads:[~2022-08-23 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 15:35 [TUHS] " Lars Brinkhoff
2022-08-22 16:27 ` [TUHS] " Warner Losh
2022-08-22 16:53   ` Bakul Shah
2022-08-22 16:56     ` Warner Losh
2022-08-23  5:55   ` Lars Brinkhoff
2022-08-23 13:02     ` Warner Losh [this message]
2022-09-09  5:51   ` Lars Brinkhoff
2022-09-14 17:48     ` Lars Brinkhoff
2022-09-14 21:33       ` Jan-Benedict Glaw
2022-09-15  5:45         ` Lars Brinkhoff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).