Re: Re: [SLE] Changing Runlevel Permanently
THOMAS ADAM wrote:
Hi,
I had the same problem. I edited the main "SuSEConfig" file in "/sbin" so that the init level is not changed back to init 5.
If you like, I can submit the changes.....
Why the hell changig SuSEconfig????
You can say it to YaST that you want start in RL 3. You have to choose ASCII login, an that was it...
Rene
Hey...calm down. What you're saying did not work for me. Each time I told yast I wanted to use Run-Level 3, it kept defaulting back to init 5 eachtime I re-ran yast. I looked in the SuSEConfig file (called by yast) and found that it would default to run-level 5 each time, so I simply changed the number..... Whats wrong with that??? I am allowed afterall...... --Thomas Adam
THOMAS ADAM wote:
Hey...calm down. What you're saying did not work for me. Each time I told yast I wanted to use Run-Level 3, it kept defaulting back to init 5 eachtime I re-ran yast. I looked in the SuSEConfig file (called by yast) and found that it would default to run-level 5 each time, so I simply changed the number.....
OK, OK if YaST does not want to change, then you're right with changing SuSEconfig. (but I still wonder why yast do not want to)
Whats wrong with that???
I am allowed afterall......
OK. You are. But in "normal cas", that's not the fine way to change the runlevel permanently. But if YaST does not work, then I think you have to this nasty edit.... Rene
OK. You are. But in "normal cas", that's not the fine way to change the runlevel permanently. But if YaST does not work, then I think you have to this nasty edit....
YaST won't allow fine grained control of the runlevel. It's graphical, text or you're SOL. If you want to create your own runlevels for special purposes, you have to either set CHECK_INITTAB to "no" in rc.config, or hack the suseconfig script. //Anders
THOMAS ADAM writes:
THOMAS ADAM wrote:
Hi,
I had the same problem. I edited the main "SuSEConfig" file in "/sbin" so that the init level is not changed back to init 5.
If you like, I can submit the changes.....
Why the hell changig SuSEconfig????
You can say it to YaST that you want start in RL 3. You have to choose ASCII login, an that was it...
Rene
Hey...calm down. What you're saying did not work for me. Each time I told yast I wanted to use Run-Level 3, it kept defaulting back to init 5 eachtime I re-ran yast. I looked in the SuSEConfig file (called by yast) and found that it would default to run-level 5 each time, so I simply changed the number.....
The place to change it would /etc/inittab. Near the top you will see a line like: # default runlevel id:5:initdefault: Change the 5 to 3, and then you can type 'init 3' as root or reboot. Now I have seen yast change stuff I have modified back, so in /etc/rc.config there is a variable: # Some people don't want SuSEconfig to modify the system. With this # entry you can disable SuSEconfig completely. # Please don't contact our support if you have trouble configuring your # system after having disabled SuSEconfig. (yes/no) # ENABLE_SUSECONFIG="no" Notice the warnings. I am pretty comfortable modifying stuff myself.
Whats wrong with that???
I am allowed afterall......
--Thomas Adam
On Monday 10 Dec 2001 2:44 pm, Jesse Marlin wrote:
THOMAS ADAM writes:
Hey...calm down. What you're saying did not work for me. Each time I told yast I wanted to use Run-Level 3, it kept defaulting back to init 5 eachtime I re-ran yast. I looked in the SuSEConfig file (called by yast) and found that it would default to run-level 5 each time, so I simply changed the number.....
The place to change it would /etc/inittab. Near the top you will see a line like:
# default runlevel id:5:initdefault:
Change the 5 to 3, and then you can type 'init 3' as root or reboot. Now I have seen yast change stuff I have modified back, so in /etc/rc.config there is a variable:
# Some people don't want SuSEconfig to modify the system. With this # entry you can disable SuSEconfig completely. # Please don't contact our support if you have trouble configuring your # system after having disabled SuSEconfig. (yes/no) # ENABLE_SUSECONFIG="no"
Notice the warnings. I am pretty comfortable modifying stuff myself.
Maybe you are. But that seems like using a sledgehammer to crack a nut.
For what is trying to be achieved (suseconfig clobbering inittab) it makes
much more sense just to set
CHECK_INITTAB="no"
which specifically addresses the issue being discussed, while leaving the
rest of the behaviour required by Yast, in place.
--
Tim Harrell
<snip>
Notice the warnings. I am pretty comfortable modifying stuff myself.
Maybe you are. But that seems like using a sledgehammer to crack a nut. For what is trying to be achieved (suseconfig clobbering inittab) it makes much more sense just to set CHECK_INITTAB="no"
You are right, the other var is overkill for this situation.
which specifically addresses the issue being discussed, while leaving the rest of the behaviour required by Yast, in place. -- Tim Harrell
participants (5)
-
Anders Johansson -
Jesse Marlin -
Rene Engelhard -
THOMAS ADAM -
Tim Harrell