From: Jody Bruchon <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: ELKS doesn't seem to like large executables
Date: Fri, 09 Mar 2012 02:44:12 -0500 [thread overview]
Message-ID: <4F59B4CC.10301@jodybruchon.com> (raw)
I haven't pinned the cause, but in working on the "BusyELKS" utilities,
I have created programs that are over 64K in total size, with segments
below 64K in size (as required by ld86). However, upon experimenting
with replacing "init" with a link to /bin/busyelks1 (which of course
contains "init") the system will boot up to the point that it tries to
load init, then just plain dies. Upon turning on some debugging
messages, I saw that it effectively crashes the system because it not
only fails to start init, it also kills "PID 0" which is supposedly the
ELKS process scheduler. Just to be clear, these programs work using the
native "elksemu" program on my Linux-i386 system. I can only assume
there's a nasty bug in how ELKS loads executables.
Anyone have a clue what might be going on?
Jody Bruchon
reply other threads:[~2012-03-09 7:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F59B4CC.10301@jodybruchon.com \
--to=jody@jodybruchon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).