From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Tue, 8 Dec 2015 21:33:54 -0600 [thread overview]
Message-ID: <5667A122.3040303@gmail.com> (raw)
All,
According to "Setting Up Unix - Seventh Edition", by Haley and Ritchie:
The best way to convert file systems from 6th edition (V6) to 7th
edition (V7) format is to use tar(1). However, a special version of tar
must be prepared to run on V6.
The document goes on to describe a reasonable method to make v6tar on v7
and copy the binary over to the v6 system. I successfully built the
v6tar binary, which will execute in the v7 environment. I then moved it
over to the v6 system and did a byte compare on the file using od to
dump the octal bytes and then comparing them to the v7 version. The
match was perfect.
The problem is this, when I attempt to execute the v6tar binary on the
v6 system (it works in v7) it errors out:
v6tar
v6tar: too large
on the v7 system, it works:
v6tar
tar: usage tar -{txru}[cvfblm] [tapefile] [blocksize] file1 file2...
I don't think the binary is too large, is is only 18148 bytes.
ls -l v6tar
-rwxrwxrwx 1 root 18148 Oct 10 14:09 v6tar
Help. First, what does too large mean? Second, does this sound familiar
to anyone? etc.
Thanks,
Will
next reply other threads:[~2015-12-09 3:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 3:33 Will Senn [this message]
2015-12-09 4:53 Noel Chiappa
2015-12-09 14:38 ` Will Senn
2015-12-09 14:56 ` Clem Cole
2015-12-09 15:07 ` Clem Cole
2015-12-09 16:29 ` Will Senn
2015-12-09 14:59 ` Hellwig Geisse
2015-12-09 17:55 ` Will Senn
2015-12-09 5:17 Noel Chiappa
2015-12-09 5:55 ` Mark Longridge
2015-12-09 11:31 ` Ronald Natalie
2015-12-09 13:30 Noel Chiappa
2015-12-09 14:43 ` Ronald Natalie
2015-12-09 20:41 ` Dave Horsfall
2015-12-09 14:24 Noel Chiappa
2015-12-09 14:56 Noel Chiappa
2015-12-09 16:37 ` Will Senn
2015-12-09 17:50 Noel Chiappa
2015-12-09 18:06 ` Will Senn
2015-12-09 22:01 Noel Chiappa
2015-12-09 22:16 Noel Chiappa
2015-12-09 22:31 ` Clem Cole
2015-12-09 22:47 ` John Cowan
2015-12-09 23:39 ` Steve Nickolas
2015-12-10 0:24 ` Clem Cole
2015-12-10 0:23 ` Clem Cole
2015-12-10 1:08 ` Greg 'groggy' Lehey
2015-12-10 9:42 ` Jacob Ritorto
2015-12-10 1:19 ` John Cowan
2015-12-10 10:06 ` Oliver Lehmann
2015-12-10 19:50 ` Will Senn
2015-12-10 4:50 Noel Chiappa
2015-12-19 13:27 Noel Chiappa
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=5667A122.3040303@gmail.com \
--to=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).