Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1742
Summary: | lilo can fail to install. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Jeremiah Johnson <jjohnson> |
Component: | installer | Assignee: | Matt Wilson <msw> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | 2, wtlovely |
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: | 1999-09-25 03:47:49 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
Jeremiah Johnson
1999-03-24 17:01:01 UTC
this one looks nasty Matt. *** Bug 1334 has been marked as a duplicate of this bug. *** Lilo warnings are not shown to the user if they occur during installation. As some lilo warnings indicate a serious problem you can easily get caught out and lock up your machine. ------- Additional Comments From gafton 03/18/99 19:40 ------- assigned to msw *** Bug 1451 has been marked as a duplicate of this bug. *** At the end of the install for 5.2 the user is asked where lilo should be installed. I selected Master Boot Record. The write of the loader to the Boot Record failed. I tried and tried to install lilo via the normal install. Eventually I found that the installer had written a lilo.conf file that was too big to be written to the boot sector. So I removed some entries and then ran lilo. I would think that a safeguard would be in place to keep lilo.conf from growing to be too big. ------- Additional Comments From msw 04/01/99 00:57 ------- it's not that the lilo entries were too big - it's probably that there was an entry for "dos" in the lilo configuration pointing at a dos filesystem that didn't have a valid boot block on it. |