mkinitrd (2 questions)

[Ricardo Carrano]

Thank you, Michael!

On Fri, Jun 6, 2008 at 6:34 PM, Michael Stone <michael at laptop.org> wrote:
> I believe that Pilgrim removes /sbin/mkinitrd.

Isn't it the case of rebuilding the base (rpm --rebuilddb) before
packing a build? I wonder if an incorrect database could cause
problems when we use yum, for instance. But I am probably missing some
important elements of the story.


>
> Ramdisks contain several kernel modules in a /lib hierarchy. When the
> kernel name changes, the /lib inside the ramdisk needs to be updated.
> You can do this manually with cpio, find, gzip/zcat, and with the kernel
> modules installed by the kernel RPM.
>
> Perhaps we could modify mkinitrd to do the right thing for us?

Michael,
Is this what you mean (taken from http://wiki.laptop.org/go/Kernel_Building)?
# mkdir /tmp/X ; cd /tmp/X
# zcat /versions/boot/current/boot/olpcrd.img | cpio -i
# rm -r lib/modules
# cp -r /lib/modules lib/
# find . -print | cpio -H newc -o | gzip -9 >
/versions/boot/current/boot/olpcrd.img
Can we make this part of the rpm build process (as described in
http://wiki.laptop.org/go/Rebuilding_OLPC_kernel).
I mean, could we build a kernel rpm that included a new olpcrd.img?

>
> Michael
>