Bug 109813
Summary: | firstboot causes console output to die in run level 3 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | firstboot | Assignee: | Brent Fox <bfox> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 1 | ||
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-12-18 22:25:49 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
Jesse Keating
2003-11-12 00:51:23 UTC
Yep, I just confirmed. If firstboot is set to _not_ run at run level 3, and only run level 5, console output is as expected. More concerning is that I have scripts in rc.local that have a read command, to get some information from the person at the system (internal first-boot configuration stuff). When firstboot tries to run at run level 3, it seems to send these read commands null returns, and really messes w/ the scripts I have set up. Firstboot now has a text mode that will run in runlevel 3. I added this to cvs a few weeks ago. This should make the problem go away. Closing as Rawhide. |