* ELKS doesn't seem to like large executables
@ 2012-03-09 7:44 Jody Bruchon
0 siblings, 0 replies; only message in thread
From: Jody Bruchon @ 2012-03-09 7:44 UTC (permalink / raw)
To: linux-8086
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-03-09 7:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-09 7:44 ELKS doesn't seem to like large executables Jody Bruchon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox