Bug 470655 - liveinst forces switch from text (runlevel 3) to graphical (runlevel 5)
liveinst forces switch from text (runlevel 3) to graphical (runlevel 5)
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-08 07:30 EST by Paul Bolle
Modified: 2008-11-08 16:20 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-08 16:20:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Bolle 2008-11-08 07:30:29 EST
Description of problem:
If liveinst is invoked in text mode (runlevel 3) it will ultimately invoke anaconda. Somewhere anaconda will switch the system to graphical mode (runlevel 5).

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

How reproducible:

Steps to Reproduce:
1. Launch F10-Beta-i686-Live.iso (in my case from QEMU)
2. Edit the command line (in SYSLINUX, I guess) to boot in runlevel 3 (text mode)
3. start liveinst
Actual results:
Somewhere anaconda will switch to graphical mode (and thus switching to runlevel 5).

Expected results:
Stay in text mode (runlevel 3). 

Additional info:
If anaconda is called with the --text option it stays in runlevel 3. (Maybe the --cmdline option does that too.) 

Would it be possible for liveinst to somehow determine it is running in textmode and add the --text option (or maybe the --cmdline option) when it calls anaconda? Would that break other use cases?
Comment 1 Jeremy Katz 2008-11-08 16:20:58 EST
It doesn't switch to runlevel 5, but anaconda defaults to running X as that's the best and most effective way of doing an installation.  You can force a text install if that's what you prefer with 'textinst'

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