Eric [EMAIL PROTECTED] wrote: ... > > How would such a thing be implemented for all binaries? Cramfs is ro so > you can't populate a loop mounted cramfs. This would mean that you either > put all /bin, /sbin, ... binaries in seperate cfs files and don't have > packages anymore, put a "bin.cfs" in every package containing the binaries > and make tons of mount points or create a cramfs within your running > system from the loaded packages and still need the initial amount of RAM > ...
IMHO LEAF should have some kind of a firmware which holds most libraries and binaries of a certain release. Maybe we need firmware sets to satisfy Joe Average. Long time ago I almost went crazy before I discovered that the ipsec package did _not_ contain ipsec.o. So there is no consistent package scheme anyway. > > Besides, you can also lzma your programs and have the same space savings. What about libraries? > > How do you see a way to create f.e. bin.cfs and still be able to install > packages? Packages should consist mostly of configuration data. Backing up, for example, root.lrp is most of the time a pain in the butt. The same applies to initrd, ipsec, ssh and others. They are just big. Few people need to change the full content of a .lrp file. Most often we just configure /etc/network/interfaces and a small number of files in /etc/shorewall. Erich ------------------------------------------------------- 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
