From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 09:56:19 -0500 [thread overview]
Message-ID: <CAC20D2PdNDRQ17whxxd5GEqaiG6px-NM58Q6xe4g7khzMsx+dw@mail.gmail.com> (raw)
In-Reply-To: <56683CDF.10609@gmail.com>
dd if=v6tar bs=128 count=1 | od
check the man page on the a.out format.
BTW: I would relink v6tar to be a "407" header so it will run anywhere.
That said, there are a number of copies of v6tar "in the wild" - my memory
is that it's on a late 1970's, very early 1980s USENIX tape.
On Wed, Dec 9, 2015 at 9:38 AM, Will Senn <will.senn at gmail.com> wrote:
> On 12/8/15 10:53 PM, Noel Chiappa wrote:
>
>> > From: Will Senn <will.senn at gmail.com>
>>
>> > 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
>>
>> That's an error message from the shell; the exec() call on the command
>> ('v6tar') is returning an ENOMEM error. Looking in the kernel, that comes
>> from
>> estabur() in main.c; there are a number of potential causes, but the most
>> likely is that 'v6tar' is linked to be split I+D, and your V6 emulation
>> is on
>> a machine that doesn't have split I+D (e.g. an 11/40). If that's not it,
>> please dump the a.out header of 'v6tar', so we can work out what's
>> causing the
>> ENOMEM.
>>
>> Noel
>>
> That was it. Thanks for supplying the logic trail you followed as well! I
> "upgraded" to a 11/70 w/2M of RAM and FPP by passing the appropriate SimH
> commands and then I folllowed the instructions in Setting up Unix Sixth
> Edition to use the m45.s assist and voila, v6tar works. Thank you.
>
> Now, when you say dump the a.out header, how do you do that?
>
> Thanks,
>
> Will
>
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151209/3ea32ab9/attachment.html>
next prev parent reply other threads:[~2015-12-09 14:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 4:53 Noel Chiappa
2015-12-09 14:38 ` Will Senn
2015-12-09 14:56 ` Clem Cole [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2015-12-19 13:27 Noel Chiappa
2015-12-10 4:50 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-09 22:01 Noel Chiappa
2015-12-09 17:50 Noel Chiappa
2015-12-09 18:06 ` Will Senn
2015-12-09 14:56 Noel Chiappa
2015-12-09 16:37 ` Will Senn
2015-12-09 14:24 Noel Chiappa
2015-12-09 13:30 Noel Chiappa
2015-12-09 14:43 ` Ronald Natalie
2015-12-09 20:41 ` Dave Horsfall
2015-12-09 5:17 Noel Chiappa
2015-12-09 5:55 ` Mark Longridge
2015-12-09 11:31 ` Ronald Natalie
2015-12-09 3:33 Will Senn
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=CAC20D2PdNDRQ17whxxd5GEqaiG6px-NM58Q6xe4g7khzMsx+dw@mail.gmail.com \
--to=clemc@ccc.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).