Hi, On Oct 11, 2010, at 3:56 PM, Toan Pham wrote:
> Rene, > > In one of the build scripts located at > 'http://svn.exactcode.de/t2/trunk/target/share/livecd/build_initrd.sh' > prefers > to the folder TOOLCHAIN/initramfs as the root filesystem for initrd > image, where everything be zipped/cpio to an initrd image. > This can be a little bit mis-understanding because the Linux kernel > 2.6+ also has initramfs (not initrd), that it can be > prepared and piggy backed with the kernel image (ref. <kernel > source>/Document/filesytems/ramfs-initramfs.txt). > I am also thinking of ways to prepare the real or new initramfs that > the kernel supports. This would make it easier > for someone to customize the new initramfs, without creating nasty > patches or build hooks to linux26 package. > Before then, should we change the livecd initrd buildscript to prepare > its content in TOOLCHAIN/initrdfs, instead of > TOOLCHAIN/initramfs? We already use the "new" initramfs everywhere for half a decade. René -- René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin http://exactcode.com | http://t2-project.org | http://rene.rebe.de
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
