The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 tar and 2bsd.tar
Date: Mon, 27 Jul 2020 21:14:37 -0400	[thread overview]
Message-ID: <CAC20D2PcpmUN87dM_Ncu_5pV95j23uHZRdvb=HwiOrY8K55pbQ@mail.gmail.com> (raw)
In-Reply-To: <df55323f-a661-a4d6-3290-3224d064aaef@gmail.com>

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

Will, on your local system, take the tarball and pull off Joy's tar binary
then move it over using dd and the trick with the disks. Joy's label told
you to use his program.  So try it.   By

on you mac:
tar xvf 2bsd.tar tar src/tar                           <-- the later one
because he gave you two
ls -l tar                                                        <-- you
may want a byte and block count
dd if=tar of=ucbtar bs=1b conv=sync         <-- pad to disk block size

then on simh:  att ucbtar to the rk05
and attach your tape 2bsd.tar like you did before

on v7:  dd if=/dev/rrkN of=ucbtar bs=1          <-- this should pull the
binary with the padded last block in

if you want to strip off the extra bytes, feel free but I don't think it's
going to matter.

chmod 755 ucbtar
./ucbtar vt0                         <--- see it works


If that fails, try the other tar he left you on the tape.

My guess is that the tarball Warren has was written with a more modern tar
and the old tar can not handle the tar threaded tape directory.  This is
possible as a lot was added to later versions tars and it's clear this is
not exactly the tape image that Joy wrote/distributed.  So, Ken's original
version might just be unable to handle it.  Hopefully, it is the contents,
but it was not written with Joy's 'tarit' script and maybe not on a V7/2BSD
system.

Clem

On Mon, Jul 27, 2020 at 8:41 PM Will Senn <will.senn@gmail.com> wrote:

> I'm trying to get 2bsd.tar extracted into v7. Does anyone have any
> recollection how to do this. Here's what I'm seeing:
>
> in simh:
> simh> att  tm0 -V -F TAR 2bsd.tar
> Tape Image '2bsd.tar' scanned as TAR format.
> contains 4935680 bytes of tape data (482 records, 1 tapemarks)
> c
>
> and in v7:
> tar xv0
> tar: bin/ - cannot create
> directory checksum error
> # ls
> bin
>
>
> What gives - it says it can't create the dir, but it does, it's there...
>
> Thanks,
>
> Will
>
> --
> GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF
>
>

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

  reply	other threads:[~2020-07-28  1:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  0:39 Will Senn
2020-07-28  1:14 ` Clem Cole [this message]
2020-07-28  3:02   ` Will Senn
2020-07-28  3:20     ` Will Senn
2020-07-28  3:21       ` Clem Cole
2020-07-28  3:47         ` Will Senn
2020-07-28  3:55           ` Will Senn
2020-07-28 13:38             ` Will Senn
2020-07-28 13:50               ` Clem Cole
2020-07-28  3:20     ` Clem Cole

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='CAC20D2PcpmUN87dM_Ncu_5pV95j23uHZRdvb=HwiOrY8K55pbQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@gmail.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).