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: Mon, 27 Jul 2020 22:55:04 -0500 [thread overview]
Message-ID: <f680ad79-8cb9-383a-9777-57f70745f9a4@gmail.com> (raw)
In-Reply-To: <5d2dd1bb-4c4e-6799-47f5-12faae521eb0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]
On 7/27/20 10:47 PM, Will Senn wrote:
> On 7/27/20 10:21 PM, Clem Cole wrote:
>> try 1b for the blocking.
> Hmm:
> dd if=/dev/rrk0 of=ucbtar bs=1b
> no space on dev 6/0
> write: No space left on device
> 1175+0 records in
> 1175+0 records out
>
> ls -l
> -rw-rw-r-- 1 root 601088 Dec 31 19:41 ucbtar
>
> df
> bad free count, b=1
> /dev/rp0 0
>
> yeah, well no kidding, that file is WAY bigger than the file on the
> host. so...
>
> rm ucbtar (or bad things WILL happen with no space left)
>
> set bs explicitly on the mac side of things
> dd if=tar of=ucbtar bs=512 conv=sync
> 27+1 records in
> 28+0 records out
>
> ls -l
> -rwxr-x--- 1 wsenn staff 14156 Jul 27 22:32 tar
> -rw-r--r-- 1 wsenn staff 14336 Jul 27 22:44 ucbtar
>
> so back in v7:
>
> set bs explicity and # blocks to read (otherwise it reads past the
> size of the file, simh quirk?)
> dd if=/dev/rrk0 of=ucbtar bs=512 count=28
> 28+0 records in
> 28+0 records out
>
> # chmod 0755 ucbtar
> # ls -l
> total 28
> -rwxr-xr-x 1 root 14336 Dec 31 19:47 ucbtar
>
> # ./ucbtar x
> tar: bin/ - cannot create
> directory checksum error
> echo $?
> 2
>
> Haha, I'm learning, but I wanna cry :).
>
>
And the other copy of tar:
ucbtar x
Tar: blocksize = 20
tar: bin/ - cannot create
directory checksum error
# echo $?
2
Ah well, I'll pick it back up tomorrow. I remember doing this on v6. I'm
gonna see if I can dig up some old notes. Maybe I unpacked the tar on
the host and used simtools to repack as magtape... just seems like this
oughta work.
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 3002 bytes --]
next prev parent reply other threads:[~2020-07-28 3:56 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 [this message]
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=f680ad79-8cb9-383a-9777-57f70745f9a4@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).