Bug 149685
Summary: | inittab not honored | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joseph A. Farmer <jfarmer99> |
Component: | rhgb | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED CANTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-14 15:45:24 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
Joseph A. Farmer
2005-02-25 06:15:07 UTC
It just dawned on me what is doing this. That is what "RHGB" in Grub is: Red Hat Graphical Boot right? The solution to this bug is have RHGB read inittab and if it sees a text based runlevel selected, not run. Viola. Of course removing RHGB from Grub would have worked but I didn't know what was doing it. I do now. I still think inittab is the "well known" way to do runlevels and RHGB should honor it. rhgb *should* be reading /etc/inittab. If it's not, it's a bug. Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you! The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to CANTFIX, however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance. (this message is mass message) |