From: will.senn@gmail.com (Will Senn)
Subject: [TUHS] v6tar from v7 on v6, too large?
Date: Wed, 9 Dec 2015 11:55:06 -0600 [thread overview]
Message-ID: <56686AFA.1080205@gmail.com> (raw)
In-Reply-To: <20151209045357.8573718C0C5@mercury.lcs.mit.edu>
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
Noel,
I followed the thread you provided and I appreciate the direction.
estabur(who thought these names up, I know 8 characters is limiting, but
c'mon) is indeed the culprit:
if(sep) {
if(cputype == 40)
goto err;
I'm gathering (read still investigating) that the 411 header is read by
a loader and the call to estabur is made with a value for sep indicating
that it is a split I+D binary, then the cputype is checked and sure
enough, it's a PDP-11/40 and the error is generated.
Thanks,
Will
next prev parent reply other threads:[~2015-12-09 17:55 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
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 [this message]
-- 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=56686AFA.1080205@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).