Quote:
Originally Posted by Drakeo
the /usr/share/mkintrid script is the real issue it reads the running kernel so this is not going to help me. Been here before.
|
That's why you are able to tell
/usr/share/mkinitrd/mkinitrd_command_generator.sh the kernel that you wish to use.
You would use something
similar to
Code:
$(/usr/share/mkinitrd/mkinitrd_command_generator.sh -k ${RELEASE} -r -a "-o /boot/initrd.gz.${RELEASE}")
to build the initrd.
Getting the lilo entry correct is slightly trickier and should look
similar to:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -a "-o /boot/initrd.gz.${RELEASE}" --lilo /boot/vmlinuz-${RELEASE} >>/etc/lilo.conf
Similar is underlined since I haven't tested both of these commands. (I'm on a Mac at work at the moment.)
