Hi Mike, > Eric, > We load and write to a compressed image currently. Initramfs is just a > cpio image. I thought we could remove some complexity. > We write to a gzip compressed loop mounted minix filesystem, we could indeed remove a bit of complexity. We could also use a gzip compressed romfs to have the same level of complexity as with a cpio image. But like romfs, initramfs is read only (AFAIK) so has the drawback of not being able to populate /dev before tmpfs in linuxrc. Besides, cpio is a seperate program (adding size) while we currently are using gzip for both initrd as the packages.
> e.g. initramfs --> ramfs/cramfs --backup--> cpio initramfs image > Both ramfs and cramfs are read only and need big (especially cramfs) programs to make backup possible. We tested with romfs which userspace fs creation program is smaller than (c)ramfs. > Probably just a bad WAG by me. Sorry I brought it up. :-( > No problem, interesting discussion :-) 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 [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
