Description of problem:
I upgraded (from redhat 7.3, I believe) an installation that used the lilo
bootloader with the line "single-key" in lilo.conf.
When the installer modified lilo.conf, it added a new entry with a long label
(not a single character).
I presume that when it ran lilo, that failed (certainly, when I booted the
rescue toolkit and tried to run lilo, it failed).
The result was that after the upgrade, there was no sign of the new installation.
Version-Release number of selected component (if applicable):
I don't want to try to reproduce it, but I would guess that it's easy to do so.
Steps to Reproduce:
Can you provide the complete traceback you received?
I don't believe I got a traceback. The installation appeared to complete
successfully, but when it booted aferwards, it booted the old (pre-upgrade) kernel.
Can you provide what your lilo.conf looked like?
I think that this is what I ended up with in lilo.conf after the installation
completed. I made it work by commenting-out the line "single-key" and re-running
lilo. I believe the installer added the block
"image=/boot/vmlinuz-2.6.16-1.2122_FC5" and changed the line "default=" and left
everything else the same.
prompt # display boot prompt
#vga=6 # vga 50 line mode
timeout=50 # 5 sec timeout
single-key # use single keypress, no return reqrd
append="idebus=66 pci=biosirq root=LABEL=/"
I am unable to reproduce this problem. If you continue to experience it with
later releases of Fedora, please feel free to reopen this bug report.