From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] more corrections
Date: Thu, 01 May 2008 13:22:53 -0400 [thread overview]
Message-ID: <30972.1209662573@mini> (raw)
In-Reply-To: <Pine.BSI.4.64.0805010707340.20990@malasada.lava.net>
Tim Newsham wrote:
>> I made some more minor corrections; turns out the commands in e00-01
>> around "4;4" are wrong, those lines are needed or the IOT dispatch
>> vector ends up in the wrong place.
>
>Hmm.. those "/" comment characters are definitely not hand written
>in. There are hand written comments that state what address things
>should land at. I'm a bit confused how this could happen with
>those comment characters in place, though, so removing them does
>sound like its the right thing to do.
now you've convinced me it's not :-)
I wonder... hmmm. if the V1 a.out header where 12 bytes long, then
everything would just automagically work.
The v7 a.out header is 16 bytes long; but could the v1 a.out header
have been 12 bytes long?
-brad
next prev parent reply other threads:[~2008-05-01 17:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
2008-05-01 21:18 ` [Unix-jun72] 11/20 handbook Al Kossow
2008-05-01 23:09 ` Hellwig Geisse
2008-05-01 22:23 ` [Unix-jun72] Early a.out headers Warren Toomey
2008-05-01 22:28 ` Warren Toomey
2008-05-01 23:01 ` Al Kossow
[not found] ` <Pine.BSI.4.64.0805011927100.20114@malasada.lava.net>
2008-05-02 10:24 ` [Unix-jun72] more corrections Brad Parker
2008-05-01 17:44 James A. Markevitch
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=30972.1209662573@mini \
--to=brad@heeltoe.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).