Bug 11513
Summary: | Cannot select different kernels through serial console at boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | david |
Component: | lilo | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
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: | 2003-06-29 20:31:34 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
david
2000-05-18 18:48:13 UTC
Do you still experience this in newer releases of Red Hat Linux? I found that if I remove this line in /etc/lilo.conf message=/boot/message then I am able to select different kernels and pass boot options to lilo from a serial console session. But with that line in lilo.conf, it causes lilo to boot the first available kernel immediately without giving a boot prompt. This is true for all of the 7.x versions I have tried. Yes, message= conflicts with serial. Anaconda will now only set up one or the other. Changing lilo so that you can have both isn't likely to happen as GRUB is our recommended boot loader these days. |