Bug 473228
Summary: | plymouth called even if not installed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Patrice Dumas <pertusus> |
Component: | initscripts | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | mcepl, mcepl, notting, rvokal |
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: | 2008-12-01 15:56:27 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
Patrice Dumas
2008-11-27 08:52:42 UTC
There is nothing to triage here (although I have some thoughts about this bug :)). Switching to ASSIGNED so that developers have responsibility to do whatever they want to do with it. If you removed plymouth, you have also then removed mkinitrd, and probably broken your system in a variety of ways. plymouth isn't optional. My system doesn't seem to be more broken than usuall. Indeed I had to remove mkinitrd, which is admitedly adventurous. But I really wanted to get rid of plymouth to check if it was the culprit for a bug (though I don't remember at all the details). In the init scripts, there are checks for plymouth and plymouth isn't called if not there. Looks sane to me and not complicated. Couldn't the same been done in the initrd? And then it would be nice not to have a hard dependency of mkinitrd on plymouth, but rather have mkinitrd use it if present. there are already switches in mkinitrd to avoid bundling too much modules, maybe a --omit-plymouth would be nice, and it would be the default in case plymouth files are missing. (In reply to comment #3) > In the init scripts, there are checks for plymouth and plymouth isn't called if > not there. Looks sane to me and not complicated. Couldn't the same been done in > the initrd? Probably simpler to just add the hard requires. > And then it would be nice not to have a hard dependency of mkinitrd on > plymouth, but rather have mkinitrd use it if present. there are already > switches in mkinitrd to avoid bundling too much modules, maybe a > --omit-plymouth would be nice, and it would be the default in case plymouth > files are missing. It is NOT OPTIONAL. This has already been discussed many times on the lists. |