Did an up2date upgrade to Seawolf from QA0404. Machine is dual boot with default boot target as the dos partition. Up2date modification of lilo.conf resulted in a new boot target (linux.bak) that is the old kernel, which boots ok. The new kernel is given the boot target of 'linux' -- which won't boot because no 'root=' entry is provided. BUT the linux boot-target is marked as the default, instead of the dos target used before. My _new_ lilo.conf as given to me by the up2date system is: --------------------------------------------- boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/boot/vmlinuz-2.4.2-0.1.49 label=linux.bak read-only root=/dev/hda3 other=/dev/hda1 label=dos image=/boot/vmlinuz-2.4.2-2 label=linux read-only The old one was: ------------------------ boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=dos image=/boot/vmlinuz-2.4.2-0.1.49 label=linux read-only root=/dev/hda3 other=/dev/hda1 label=dos -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
I believe this was fixed in 0408. Adrian, can you verify?
This is fixed in the latest up2date-2.5.3-1 which should be going out as soon as it makes it way through QA.