Encountered a problem with lilo.conf when upgrading a 3.0.3 system to qa0308.0. The lilo.conf that anaconda wrote would not boot properly since the old 3.0.3 kernel was still trying to load. Here is the lilo.conf from the 3.0.3 system before upgrade (taken from lilo.conf.rpmsave) boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 image=/vmlinuz label=linux root=/dev/hda5 read-only Here is the lilo.conf as written by anaconda for post reboot boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/vmlinuz label=linux root=/dev/hda5 read-only As you can see the old kernel is still being used as the default image. It should read image=/boot/vmlinuz to boot the new 2.4.2 kernel instead of the old 1.2.13 kernel.
Created attachment 12202 [details] old lilo.conf file (lilo.conf.rpmsave)
Created attachment 12203 [details] new lilo.conf file
This defect considered MUST-FIX (show-stopper) for Florence Gold
Fixed in cvs.
*** Bug 28280 has been marked as a duplicate of this bug. ***
*** Bug 26790 has been marked as a duplicate of this bug. ***
*** Bug 26910 has been marked as a duplicate of this bug. ***