Bug 82499
Summary: | Firstboot is started in runlevel 3? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Bernd Bartmann <bernd.bartmann> |
Component: | firstboot | Assignee: | Brent Fox <bfox> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | mitr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-05-25 14:30:21 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
Bernd Bartmann
2003-01-22 21:17:52 UTC
No, it's supposed to pop up a text-based dialog asking if you want firstboot to run or not. Something is wrong in the initscript because the chars are being sent to /var/log/messages instead of starting the tui interface. I'm trying to sort it out. I've run out of time to fix this properly. I've changed firstboot so that if it detects that the machine is booting into runlevel 3, it assumes that you don't want to see firstboot at all, so it writes the /etc/sysconfig/firstboot file and disables the initscript with chkconfig so that firstboot is never run. Should be implemented in firstboot-1.0.5-1. There is a stack of 64 bugs that have been in Modified state for a long period of time. I am closing these as Rawhide now. If you find that the issue is not fixed, please reopen this report. |