|
From: Erich T. <eri...@th...> - 2005-08-24 09:18:59
|
Eric E.S...@in... wrote: > > 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. Yes, but look at it when it holds ipsec, ssh, samba, squid... A loop mounted cramfs looks (for read_only operations) exactly like a part of the file system tree. The benefit of this is that, even on ram, it cannot be trivially modified and it takes a lot less RAM space because it compresses its contents. For example if we had all the /bin in a cramfs called bin.cfs which would sit at / we could mount mount -o loop /bin.cfs /bin and the space needed by bin.cfs would be a lot smaller than if the individual files in /bin would be installed normally. The same is true for all read_only components, like /lib /sbin /usr/bin cheers Erich |