/vmlinuz /initrd.img links

ninj4fly · 02-19-2008, 03:17 AM

Hi,

Does someone know reasons for the /vmlinuz{,.old} and /initrd.img{,.old} links (pointing to the actual kernel and initrd image under /boot) existence? In Debian there is a configuration file /etc/kernel-img.conf where I can set do_symlinks=no and those links should not be created and updated anymore. Can I safely set this option to "No" and remove those links? Should this prevent the machine to boot/upgrade correctly or interfere with other services of applications?

Thanks

billymayday · 02-19-2008, 03:34 AM

Probably used by grub. What's in /boot/grub/menu.lst

ninj4fly · 02-19-2008, 03:49 AM

#########################################################
title Debian GNU/Linux, kernel 2.6.18-4-686
root (hd0,1)
kernel /vmlinuz-2.6.18-4-686 root=/dev/sda3 ro
initrd /initrd.img-2.6.18-4-686
savedefault
#########################################################

Here are the actual kernel and initrd.img versions, and not the links that lack version number in the filename. I think grub takes the path relatively to the /boot directory. Or may be I'm wrong?

pixellany · 02-19-2008, 07:31 AM

Quote:

Originally Posted by ninj4fly

Here are the actual kernel and initrd.img versions, and not the links that lack version number in the filename. I think grub takes the path relatively to the /boot directory. Or may be I'm wrong?

The root statement tells grub which partition contains /boot. The paths are relative from there.

I always softlink the kernel and initrd files, so that I can use the shorter names in menu.lst.

eg ln -s vmlinuz<stuff> vmlinuz
then the menu.lst entry will be kernel /path/vmlinuz

ninj4fly · 02-19-2008, 08:33 AM

Thanks for the explanation pixellany. The main question still remains. Is it save to remove /vmlinuz and /initrd.img links and change the /etc/kernel-img.conf file so that they should never be created again on update.

Thanks