Bug 398871
Summary: | firstboot initscript chkconfig not turned 'off' after first boot | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Karsten Wade <kwade> |
Component: | firstboot | Assignee: | Chris Lumens <clumens> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
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: | 2007-11-27 19:28:16 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
Karsten Wade
2007-11-25 23:16:21 UTC
It's intentional that the firstboot in f8 does not chkconfig itself off, as this was a workaround for some corner case involving the timeout on the text firstboot interface. In f8 it's not doing anything other than checking if it needs to run and then bailing out, so there's not really any harm. Regardless, the next release of firstboot that I am testing in Rawhide will chkconfig off itself after running to completion so this bug will be fixed there. |