Bug 23056
| Summary: | single-key in lilo.conf confuses lilo install | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | fred-m |
| Component: | installer | Assignee: | Brock Organ <borgan> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-01-08 17:26:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Assigning to a developer. Fixed in CVS using qa0110.0 internal test tree, verified system w/alias (as above) is now bootable: old lilo.conf: boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=foobar image=/boot/vmlinuz-2.2.16-22 label=foobar read-only root=/dev/hda1 image=/boot/vmlinuz-2.2.16-22 label=new alias=l single-key read-only root=/dev/hda1 post upgrade lilo.conf: boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/boot/vmlinuz-2.4.0-0.43.12 label=linux initrd=/boot/initrd-2.4.0-0.43.12.img read-only root=/dev/hda1 Note that there is NO alias info in the upgraded lilo.conf, but the system is bootable and the old version IS saved as /etc/lilo.conf.rpmsave ... so the next release of Red Hat Linux will handle this condition better ... thanks for your report! |
My lilo.conf had the following setup for Linux: label=new alias=l single-key When I upgraded to Red Hat 7.0, I chose the default configuration given by the installer ("dos" and "linux"). However "linux" clashed with "alias=l", lilo didn't write the boot sector, and for short the computer didn't boot after the update. Deleting the single-key setup and re-running lilo from the CD-ROM in recovery mode solved the problem. (If I was upgrading in "expert" mode I would even say that this was my fault, but in non-expert mode it would be nice if this and other lilo errors were caught).