From: wkt@tuhs.org (Warren Toomey)
Subject: [Unix-jun72] 0407 binaries on 1ed
Date: Mon, 5 May 2008 08:33:53 +1000 [thread overview]
Message-ID: <20080504223353.GA63333@minnie.tuhs.org> (raw)
In-Reply-To: <Pine.BSI.4.64.0805031940510.20114@malasada.lava.net>
On Sun, May 04, 2008 at 10:18:08AM -1000, Tim Newsham wrote:
> I added a patch "aout407.patch" for running a.out binaries in the 1ed
> kernel. It could be a little cleaner; if anyone can review it and fix
> it up I would appreciate it. I was able to run "as" and "size",
> both of which are 0407 binaries.
Excellent stuff Tim. I've had a quick look; I suspect the existing code:
cmp r5,u.count /
bgt 1f / branch if r5 greater than u.count
mov r5,u.count
checks to ensure that the new a.out is small emough to fit into the
address space left by the executable that called exec(2).
> This patch isn't applied automatically, but I also changed the
> "tools/rebuild" script to take a list of optional patches to apply.
That's also a good idea. Thanks Tim.
Warren
next prev parent reply other threads:[~2008-05-04 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 5:19 [Unix-jun72] init Tim Newsham
2008-05-04 5:31 ` Tim Newsham
2008-05-04 6:29 ` [TUHS] comparing s1 frags, s2 bits, 1ed and jun72 print out Tim Newsham
2008-05-04 20:18 ` [Unix-jun72] 0407 binaries on 1ed Tim Newsham
2008-05-04 22:33 ` Warren Toomey [this message]
2008-05-05 0:00 ` Tim Newsham
2008-05-05 1:17 ` [Unix-jun72] Another RK mount program Warren Toomey
2008-05-05 1:23 ` [Unix-jun72] No luck with C compiler yet, but an idea Warren Toomey
2008-05-05 1:56 ` Tim Newsham
2008-05-05 23:01 ` [Unix-jun72] uppercase input Warren Toomey
2008-05-04 6:50 ` [Unix-jun72] init Warren Toomey
2008-05-04 8:41 ` [Unix-jun72] Yes, a mount command Warren Toomey
2008-05-04 12:54 ` [Unix-jun72] init Brad Parker
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=20080504223353.GA63333@minnie.tuhs.org \
--to=wkt@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).