The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <>
To: Bakul Shah <>
Cc: The Eunuchs Hysterical Society <>
Subject: [TUHS] Re: Extracting files from various old dump/restore tapes
Date: Mon, 22 Aug 2022 10:56:09 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On Mon, Aug 22, 2022 at 10:53 AM Bakul Shah <> wrote:

> On Aug 22, 2022, at 9:27 AM, Warner Losh <> wrote:
> >
> > FreeBSD deleted some compat code in the kernel some time ago, and it
> turns
> > out that restore used that to read old dump tapes, so we broke old dump
> tapes.
> > So you can't use FreeBSD's unmodified.
> May be run an older release that has this code?

That only works if the dinode structures line up exactly to whatever these
are from. The 16-bit ones likely need to use the V7 restore (maybe running
emulation in simh), the 32-bit ones might be able to use V32 or 4BSD
running in
emulation, if that's what the tapes are from. But the multi-endian
suggests  that
maybe things are more complex than that.

FreeBSD's restore from older releases might work, but only for the 32-bit
stuff and
only if we're lucky...


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

  reply	other threads:[~2022-08-22 16:57 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 [this message]
2022-08-23  5:55   ` Lars Brinkhoff
2022-08-23 13:02     ` Warner Losh
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).