You could take a look at the FUZIX userspace. Much of it is far more compact and a lot of it uses write() etc for size saving. The library routines are also often a lot more memory efficient (eg the malloc is much tinier as it was rewritten after I found the ELKS one was being really buggy). There shouldn't be too much churn involved as the FUZIX libc is based in part on the ELKS one with other bits taken from MUSL and the like (and the FP library largely comes from the Sun contributions) A second option for the C library is to implement shared libraries not necessarily by truely sharing it as a library with its own cs: but using the callers ds:/ss:, as that involves some fun for fixing up callbacks, but even something as simple as loading it into the process address space from a different file when execve runs. And the third of course is to implement support for something like exomizer, that doesn't even need kernel support except for split I/D binaries. The compressor needs a big computer but the decompressor is tiny. Alan -- 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
