Bug 10993
Summary: | LILO picks incorrect drives/partitions | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Remko Molier <rmolier> |
Component: | lilo | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | 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: | 2001-04-18 21:32:14 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
Remko Molier
2000-04-23 02:16:43 UTC
Lilo is acting exactly as expected. It does not attempt to read the fstab on the / partition in order to determine what partition /boot is, it merely determines what device /boot is on by checking the existing files. It's actually easier to set a system like yours up to have a single /boot partition that is shared between both / filesystems with all needed kernels in the one /boot partition. If you don't set it up that way, then you need to mount the additional /boot filesystem as something like /boot2 and change the firewall stanza to point to /boot2/vmlinuz.... and then in the lilo.conf file in the firewall's root filesystem you would need to mount the non-firewall /boot as /boot2 also, and make the non-firewall stanza point to /boot2/vmlinuz... in order to be able to run lilo from either of the selected root filesystems. If you use a common /boot filesystem, then you can at least use identical lilo.conf files between the two booting copies of the OS. |