On Thu, 25 Nov 2004, Paul Howarth wrote:
# Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda5 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Fedora Core (2.6.9-1.3_FC2) root (hd0,0) kernel /vmlinuz-2.6.9-1.3_FC2 ro root=LABEL=/ initrd /initrd-2.6.9-1.3_FC2.img title Fedora Core (2.6.8-1.521) root (hd0,0) kernel /vmlinuz-2.6.8-1.521 ro root=LABEL=/ initrd /initrd-2.6.8-1.521.img title Red Hat Linux (2.4.20-8) root (hd0,0) kernel /vmlinuz-2.4.20-8 ro root=LABEL=/1 initrd /initrd-2.4.20-8.img
So, when a new kernel is to be added, how does grubby know whether to add an entry with "root=LABEL=/" or "root=LABEL=/1"?
this is getting dangerously close to being more relevant on the anaconda development list, no?
Not quite; grubby, the tool used to add entries to grub/lilo.conf (see "man grubby") is invoked from the post-install scripts of kernel RPMs (it's called up from /sbin/new-kernel-pkg). Anaconda may set up the initial grub.conf but all subsequent changes are done using grubby (and your favourite editor ;-) ).
Paul.
