list of 2.6-related migration issues for embedded programmers?

Linh Dang linhd at
Tue Jul 20 04:14:44 EST 2004

On 19 Jul 2004, rpjday at wrote:

> On Mon, 19 Jul 2004, Linh Dang wrote:
>> On 19 Jul 2004, rpjday at wrote:
>>> - initramfs:  currently, i'm still using a zImage.initrd-based
>>> image, and all i know about initramfs is that it's checked for at
>>> boot time.  should i care about it?  at some point, probably, i'm
>>> sure.
>> initramfs is convenient. you don't need root access nor special
>> tools to create the root-fs. it very easy when you want to
>> version-controlled you root-fs.
> ah, that would be convenient since, as it is, i'm using a hacked
> version of "genext2fs" that allows me to create the initial root fs
> as a regular user.  i *definitely* have to look into initramfs,
> then.

Don't use the .initramfs section option (the one that's linked with
with vmlinux.) Build your ramdisk.image.gz as a compressed cpio
archive. I.e. zvmlinux.initrd's .ramdisk section contains a compressed
cpio archive instead of an compressed ext2 image.


** Sent via the linuxppc-embedded mail list. See

More information about the Linuxppc-embedded mailing list