From: David Given <dg@cowlark.com>
To: "ELKS (linux-8086)" <linux-8086@vger.kernel.org>
Subject: Re: Some words of encouragement
Date: Sat, 25 Feb 2012 13:13:53 +0000 [thread overview]
Message-ID: <4F48DE91.5070203@cowlark.com> (raw)
In-Reply-To: <4F48D9CB.5050901@cowlark.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On 25/02/12 12:53, David Given wrote:
[...]
> I'm now thinking that the sanest way to go here is (a) hack Watcom to
> support ELKS executables directly; (b) write a tool to disassemble the
> OMF output and convert it to as86-compatible format; (c) give up and go
> to the pub...
Actually, I forgot option (d): change ELKS. It occurs to me that the
kernel doesn't actually need to know the BSS size. All it's doing is
allocating a data segment the size of the chmem field, loading the
preinit data from the file, and zero-initialising the rest. So all it
needs is the preinit data size, which we have, and the chmem size, which
we have. So if we're willing to decree that the kernel ignores the BSS
size field, we're good to go...
...in fact, looking at fs/exec.c, I reckon that it should work as is.
The only place the BSS size field is used in an old-style executable is
during the call to memset, where 0 is safe.
--
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│
│ "Never attribute to malice what can be adequately explained by
│ stupidity." --- Nick Diamos (Hanlon's Razor)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2012-02-25 13:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:26 Some words of encouragement Brad Normand
2012-02-24 18:22 ` Jody Bruchon
2012-02-25 0:54 ` David Given
2012-02-25 6:27 ` Brad Normand
2012-02-25 12:53 ` David Given
2012-02-25 13:13 ` David Given [this message]
2012-02-25 18:04 ` Brad Normand
2012-02-25 19:09 ` David Given
2012-02-25 20:29 ` Brad Normand
2012-02-25 21:04 ` David Given
2012-02-25 23:05 ` Brad Normand
2012-02-26 1:10 ` zkry
2012-02-25 5:12 ` Brad Normand
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=4F48DE91.5070203@cowlark.com \
--to=dg@cowlark.com \
--cc=linux-8086@vger.kernel.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