Bug 444010

Summary: we still ship /etc/inittab
Product: [Fedora] Fedora Reporter: Chris Lumens <clumens>
Component: rhgbAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-29 16:17:21 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235706    

Description Chris Lumens 2008-04-24 11:18:16 EDT
The following commit is trouble:

* Tue Mar 18 2008 Casey Dahlin <cjdahlin@ncsu.edu> - 1:0.17.7-11
- Don't check /etc/inittab for default runlevel since it may no longer be

We still ship a /etc/inittab, and this is what anaconda is writing out for now.
 What's happening is that after a text install, we have runlevel 3 in the
inittab and GRAPHICAL=yes in the /etc/sysconfig/init file.  upstart starts up in
runlevel 3 as indicated by /sbin/runlevel, but rhgb runs anyway.

The end result is that text mode firstboot starts up in the rhgb expanded
window.  That quickly dies and leaves us with a wonderful expanse of blue on the
screen and nothing else.
Comment 1 Bill Nottingham 2008-04-24 14:42:06 EDT
Fixed in 9.0.0-3.
Comment 2 Bill Nottingham 2008-04-29 16:17:21 EDT
And verified.