From: jam@magic.com (James A. Markevitch)
Subject: [Unix-jun72] more corrections
Date: Thu, 1 May 2008 10:44:38 -0700 (PDT) [thread overview]
Message-ID: <200805011744.KAA15939@mist.magic.com> (raw)
> I wonder... hmmm. if the V1 a.out header where 12 bytes long, then
> everything would just automagically work.
If you look at sysexec, you will see that the "magic number" for the
a.out header is 000405. That is an instruction that jumps over the
first 12 bytes.
James Markevitch
next reply other threads:[~2008-05-01 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 17:44 James A. Markevitch [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-01 16:09 Brad Parker
2008-05-01 17:03 ` Tim Newsham
2008-05-01 17:10 ` Al Kossow
2008-05-01 17:19 ` Brad Parker
2008-05-01 17:10 ` Tim Newsham
2008-05-01 17:22 ` Brad Parker
[not found] ` <Pine.BSI.4.64.0805010726040.20990@malasada.lava.net>
2008-05-01 17:47 ` Brad Parker
2008-05-01 17:54 ` Tim Newsham
2008-05-01 18:15 ` Tim Newsham
2008-05-01 18:21 ` Tim Newsham
2008-05-01 18:34 ` Tim Newsham
2008-05-01 22:51 ` Warren Toomey
2008-05-01 23:31 ` Tim Newsham
2008-05-01 19:02 ` John Cowan
[not found] ` <Pine.BSI.4.64.0805011927100.20114@malasada.lava.net>
2008-05-02 10:24 ` 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=200805011744.KAA15939@mist.magic.com \
--to=jam@magic.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).