From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 tar and 2bsd.tar
Date: Tue, 28 Jul 2020 08:38:00 -0500 [thread overview]
Message-ID: <dcc269e9-1213-4d36-66cf-574ad8cab326@gmail.com> (raw)
In-Reply-To: <f680ad79-8cb9-383a-9777-57f70745f9a4@gmail.com>
After much travail, I found a post in some ancient Asian language
(Japanese) and was reminded of Wolfgang's enblock. I didn't bother to
translate, but just did the enblock:
gunzip -d 2bsd.tar.gz
cat 2bsd.tar | enblock > 2bsd.tap
I attached the result, et voila:
tar xv0
tar: bin/ - cannot create
x bin/csh, 40412 bytes, 79 tape blocks
tar: bin/etc/ - cannot create
x bin/etc/htmp, 0 bytes, 0 tape blocks
x bin/etc/install, 81 bytes, 1 tape blocks
The cannot create messages are filthy lies :).
That brought it all back to me - just like when I built tar from tape
for v6... sheesh, why does it have to be so painfully difficult to
remember these tricky bits?!
Anyhow, afterward, I went back, did the translation from Japanese to
English (or google did), and it was good stuff about how to apply
2bsd.tar to v6:
https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Forumin.blogspot.com%2F2014%2F06%2Funix-and-2bsd-on-pdp11simh-2.html
Thanks for the help and patience.
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
next prev parent reply other threads:[~2020-07-28 13:38 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
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 [this message]
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=dcc269e9-1213-4d36-66cf-574ad8cab326@gmail.com \
--to=will.senn@gmail.com \
--cc=clemc@ccc.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).