ELKS doesn't seem to like large executables

[Jody Bruchon <jody@xxxxxxxxxxxxxxx>]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html