Hello Erich, >> LEAF runs in RAM, so it's not only a matter of 16 Mb storage but also >> the availability of internal RAM. This shouldn't be a problem in most >> cases, but if LEAF is ported to other architectures with limited RAM >> this could become a problem. > > Indeed, and I am surprised noone ever brought this up. Currently LEAF > (and probably other RAM based systems) is wasting RAM for storage of > binaries , libraries and scripts, some of which are loaded only once. If we > want to keep the RAM based architecture of the LEAF systems and reduce the > RAM footprint I believe we need to restructure our packages > so they can be held in a small number of loop mounted cramfs images. I > believe we could reduce the filesystem footprint significantly. LINCE does > this already AFAIK. Only the configuable files need to be held in a R/W > filesystem. > I don't follow you here. Why do you wan't to use loop mounted cramfs? Does it use RAM or ROM (Flash/HD/Floppy/..). The advantage of full RAM based systems is that you can unmount the storage media. Besides the footprint of Bering-uClibc with base packages is only ~8Mb.
Eric ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
