Re: Cleaning up elkscmd and adding help text - Questions

MFLD
2015-03-27T18:19:54Z

Hello,

I really wonder why you spend time on the ELKS userland... if I have a
look to the sizes of uclibc and busybox on a 32 bits embedded system,
built with BuildRoot, and with many features (threads, unicode, large
files, etc) that have no sense on a 8086 architecture:

-rwxr-xr-x 1 mfld mfld 296704 19 mars 09:20 libuClibc-0.9.33.2.so
-rwxr-xr-x 1 mfld mfld 633548 19 mars 09:20 busybox

Yes, it is still too large for a 1 MB address space, but don't you think
it would be worth giving a try to reduce the uclibc and Busybox
footprint, rather than doing the same job as the our friends ?

If I take the example of my 80188 system where I am playing with ELKS, I
have 512 KB of Flash, so not so far from the current size of uclibc and
busybox on my Cortex A8 system...

Regards,

MFLD

Le 27/03/2015 17:17, Jody Bruchon a Ã©crit :
> On March 27, 2015 10:10:10 AM EDT, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> And pretty soon all your apps won't fit on the floppy disc image.
>> If you are going to go that way then probably it needs "fake" shared
>> libraries.
> This was actually one of the reasons I was experimenting with "BusyELKS" since it would minimize the number of copies of statically linked code on disk. The downside is that the size of the programs overall would increase, but it wouldn't require new logic to support sort-of-shared libraries.
>
> There are a lot of programs that were directly ripped out of the sash code base and can easily share code between them since they used to be one big code unit originally. I see a lot of potential for combining the smaller tools and sharing code between them. Perhaps I should revisit that concept...?
>
> -Jody

--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html