Dear all, About caching the main filesystem of a Debian Live OS, I give a try to uloop.
I have modified live-initramfs to mount the live_media as an uloop device, creating new options for caching to RAM memory or to disk, Doing some tests I can see that works correctly, uloop shows various advantages over other forms of copying the filesystem to disk or to RAM. With that there is no delay at starting the system, since the cache is created when the Operating System needs new parts from the original media and the space used by the cache grows according to the reading from the original device. Thank you for that tool ! and all the rest of the assemble ! because my Debian Live uses squasfs+lzma and aufs also. Observing that tool, The original filesystem, by now, only could be a block device and "http" URLs. A suggestion, I propose the creation of the tool "ulofile": uloop even can be better if could exist the utility "ulofile", that will permit to mount in uloop only the main compressed file of the Live OS, with "ulofile" the Live OS could be a lot more practical and would have more possibilities. As example of other possibilites, Autoupdate: suppose mounting the live-media device with standard losetup, and a process detects the presence of new versions of the system compressed files and replacing them. Then the system files are mounted and cached with uloop. Regards, Jordi ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
