Bug 19885 - Xconfigurator changes runlevel to 7 instead of 5
Summary: Xconfigurator changes runlevel to 7 instead of 5
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: Xconfigurator   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-26 21:37 UTC by Need Real Name
Modified: 2007-03-27 03:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-26 21:37:44 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Need Real Name 2000-10-26 21:37:41 UTC
Hi folks!

I have just installed the brand new RedHat 7.0 on my Notebook. The 
installation went fine. When I executed Xconfigurator to change my video 
settings I chose to let Xconf change the default startup runlevel to 
graphic login.

Xconfigurator changed the runlevel to 7 instead of 5 so that after every 
following boot my NB went to halt right at the beginning.

This one's another example of what happens when people change low-priority 
variables (e.g. such an un-important thing like a startup runlevel)... :-)

P.S. is there any chance to boot a system that starts with runlevel 7?

Thanks for your answer and a patch...

Comment 1 Trond Eivind Glomsrxd 2000-10-26 21:53:13 UTC
There is no codepath which could give you runlevel 7 - it just isn't possible:

		if (rc & STARTX)
                    state->runLevel = 5;
		else
                    state->runLevel = 3;

(and there is one other codepath touching it for kickstart, much the same way).

Anyway, to choose runlevel 3 on boot type "linux 3" at the boot prompt.
Another option would be to use the Red Hat Linux CD in rescue mode.


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