Bug 444010 - we still ship /etc/inittab
Summary: we still ship /etc/inittab
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-04-24 15:18 UTC by Chris Lumens
Modified: 2008-05-02 17:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-29 20:17:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Lumens 2008-04-24 15:18:16 UTC
The following commit is trouble:

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

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 18:42:06 UTC
Fixed in 9.0.0-3.

Comment 2 Bill Nottingham 2008-04-29 20:17:21 UTC
And verified.


Note You need to log in before you can comment on or make changes to this bug.