Bug 6122
Summary: | Upgrade option puts LILO in the wrong place | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Joshua Rosen <bjrosen> |
Component: | installer | Assignee: | Jay Turner <jturner> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | srevivo |
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: | 2000-02-08 18:33:43 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
Joshua Rosen
1999-10-20 05:00:22 UTC
But the _expert_ upgrade path should _not_ assume lilo at all. This has been noted in asides in other bugs. There are still heritage boxes which need to use dos drivers to initiate undocumented hardware and then boot with loadlin. Not to mention the wealth of other double, triple and quadruple boot systems. The installer must request whether lilo is to be used at all, and if so, it needs to request or present the proposed lilo.conf for confirmation or modification. updates-RHEA-1999_045.img still misbehaves in this area. Assigned to jturner |