Bug 30228
Summary: | lilo doesnt rerun itself after package install | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Adrian Likins <alikins> |
Component: | lilo | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | alikins, jik, katzj |
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: | 2002-06-04 06:18:04 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: |
Description
Adrian Likins
2001-03-01 21:52:09 UTC
Since Adrian and I were talking about this some last night, there are additional complications. The first thought of complication is initial install, but that's a "easy" case as /etc/lilo.conf doesn't exist until it's created by the installer. But, even if you check that lilo.conf exists, it could still be invalid already if an updated kernel has been installed before the updated lilo in the case of updating either via anaconda or up2date. I'd like to second this bug. It's sort of axiomatic that a package upgrade shouldn't break a machine, and yet when you install a lilo package your machine will no longer reboot. grub gets this right, but changing the way lilo works isn't worth the effort... switch to using grub :-) (and I endorsed this bug at one point ;) |