On 11/03/2003 08:17 PM, hugh wrote:
Durung the update initrd's are created for all kernel images registered in the /boot/grub/menu.lst.
Actually, unless I miss my guess, it builds an initrd for all kernel images in /boot. I really can't speak regarding 9.0, but I am testing 2.6 with 8.2, and it required an updated mkinitrd, and that is what it does.
Once it is installed, and if I custom-compile my own kernel, I need to make the initrd-2.4.23-pre9 (e.g.) against the new kernel. and I do not know how to make it.
Actually, this really hasn't changed. Try mkinitrd -h. To do what you want, try mkinitrd -k "kernel image filename" -i "initrd filename" -m "modules included in this initrd" -s "size of splash image", i.e to build my initrd for my 2.6, I used mkinitrd -k "vmlinuz26" -i "initrd26" -m "jbd ext3 sr_mod" -s 1024x768 and it worked for me. Note this is an updated 8.2, not 9.0.
Can any one teach how to make it?
Hope the above does that.
Up to 8.2, creating a new initrd for every new custom-compiled kernel was not quite critical. It appears that things changed greatly.
For me, it appears to be the same since I started (6.2). It would vary greatly on if your kernel needs modules to see the / filesystem. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.