Bug 10990
Summary: | Automatic installation of LILO on FAT32 is just faggoty. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | dijxtra |
Component: | installer | Assignee: | David Lawrence <dkl> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
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-06-16 15:33:41 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
dijxtra
2000-04-22 18:17:21 UTC
The Workstation installations in Red Hat Linux 6.2 (both the GNOME and KDE workstations) install lilo to the MBR of the drive and add entries for other operating system which the installer finds on the system (such as Windows) So, the installation is not writing Lilo to a FAT32 partition . . . it is writing it to the MBR of the drive. Not quite sure what problem you are seeing in this particular case, but it is certainly not that Lilo was written to a FAT32 partition. |