Bug 708054

Summary: Insufficient and unformatted console boot messages
Product: [Fedora] Fedora Reporter: Russ <admin>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: harald, johannbg, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-26 16:47:31 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 Russ 2011-05-26 16:19:48 UTC 
Description of problem:
The usage of systemd in F15 provides insufficient and unformatted boot messages.

Version-Release number of selected component (if applicable):
26-1

How reproducible:
always

Steps to Reproduce:
1. Boot F15 
2. View console boot messages.
3. Are the boot messages formatted according to Red Hat standards?
"Starting <daemon>  [ok/failed]"
  
Actual results:
No! The messages do NOT conform to the RH standard boot feedback implemented since at least RH 5.0.

Expected results:
RH standard boot message feedback - i.e. "Starting <daemon>  [ok/failed]"

Additional info:
Who approved this unformatted jumble of messages? If Fedora/RHEL users wanted something like this they would just switch to Ubuntu or Debian, The clean boot message interface has been a RH standard since at least RH 5.0 and has NEVER CHANGED. Changing something such as this is almost as dramatic to us as going to dpkg format. It should NEVER be done. We are all for speeding up boot times and using a better system, but surely it is possible to display a proper boot interface also. There is not even feedback for the progress of a boot time fsck!
Please fix this mess ASAP. It can't be that difficult to format things properly and add fsck progress.
Comment 1 Michal Schmidt 2011-05-26 16:47:31 UTC 
The lack of fsck progress display is bug 679492.
A nice display of services startup is bug 622663.

*** This bug has been marked as a duplicate of bug 622663 ***