>> Hmmm.... I'm as new as 2 days on this list, and yes, I'm looking
>> ELKS as a possible embedded system also. Real embedded projects we
>> do here are using 186s and that's with 16-bit real mode only. I'm
>> even considering porting ELKS back to 32 bits for 386/486 and ARM.
>> All these are NOT supported by eCos, and I'd think that porting
>> ELKS would be simpler than porting eCos.
>
>May be it would be better to consider about original
>linux kernel applying with ARM support included ( since v 2.1 )?
Yes, it will be advantageous to compare ELKS with that and strip off
the unwanted stuff.
I'm greatly impressed by the enthusiasm of the participants on the list.
Thanks for all these feed-back!
The linux kernel is too large for embedded system. We may no want a
file system at all. One way to do this is to implement the application
as the init program called by the kernel after booting, or just find the
place
that opens and executes init and change it to run the application actually
linked with the kernel.
Commercial Embedded OSes are actually just some startup code and a
library for system calls, and links with your application as a single
binary.
----------------------------------------------
Charles Changli Chin
Technology Service Division
Institute of Information Industry
Taiwan
[EMAIL PROTECTED]
