Hello, I just made a brand-new installation of 7.3 and one of the first things I did after the install was open yast and set all my favorite 'rc' settings, one of this is DISPLAYMANAGER=console. Upon rebooting, however, it cam up as xdm in init 5. Looking at /etc/inittab I discovered that SuSEconfig had not changed inittab at all. So I changed it by hand and rebooted. That worked, but in order to test yast, I set DISPLAYMANAGER back to kdm and rebooted - again, /etc/rc.config had the right setting but inittab was not changed. This greatly worries me - if it's broken I'm going to have to re-reun the whole installation - I don' want an install that's broken. It would appear to me that it's SuSEconfig that's hurt - anyone have an ideas what I could try before reinstalling? TIA ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com
JW wrote:
Hello,
I just made a brand-new installation of 7.3 and one of the first things I did after the install was open yast and set all my favorite 'rc' settings, one of this is DISPLAYMANAGER=console.
Upon rebooting, however, it cam up as xdm in init 5. Looking at /etc/inittab I discovered that SuSEconfig had not changed inittab at all. So I changed it by hand and rebooted. That worked, but in order to test yast, I set DISPLAYMANAGER back to kdm and rebooted - again, /etc/rc.config had the right setting but inittab was not changed.
This greatly worries me - if it's broken I'm going to have to re-reun the whole installation - I don' want an install that's broken.
It would appear to me that it's SuSEconfig that's hurt - anyone have an ideas what I could try before reinstalling?
For "most" of the things in rc.config to take affect you must run SuSEconfig after changing rc.config. Mark
At 12:52 PM 2/6/2002 -0500, you wrote:
For "most" of the things in rc.config to take affect you must run SuSEconfig after changing rc.config.
Yes, that is exactly correct, however please note the following, which I obviously didn't make clear in my previous post: 1. yast runs SuSEconfig upon hitting "F10". There is no need to run SuSEconfig by hand after using yast 2. I did run SuSEconfig by hand anyway, twice, and that didn't fix the problem either - it still didn't edit /etc/inittab i.e. SuSEconfig _did_ get run, both automatically and by hand. Yet for some reason it doesn't edit /etc/inittab. Any more ideas?
Mark
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com
On Wednesday 06 February 2002 18.09, JW wrote:
Hello,
I just made a brand-new installation of 7.3 and one of the first things I did after the install was open yast and set all my favorite 'rc' settings, one of this is DISPLAYMANAGER=console.
This question made me RTFS a little. It seems in 7.3 SuSEconfig doesn't touch the runlevel setting at all. Many thanks to whoever it was that removed it. Now it is possible to have user defined run levels again without having to set CHECK_INITTAB to no. Setting DISPLAYMANAGER=console has the same effect as setting it to DonaldDuck, in other words if you're in runlevel 5 you'll get the default display manager, which is xdm. The runlevel now is only set by YaST internally, by going to System Configuration -> Login and setting "graphical" or "Ascii". Unless you prefer to edit inittab manually, that is. Of course I may have misread the source, but it is verified by experience. regards Anders
At 07:03 PM 2/6/2002 +0100, you wrote:
On Wednesday 06 February 2002 18.09, JW wrote:
Hello,
I just made a brand-new installation of 7.3 and one of the first things I did after the install was open yast and set all my favorite 'rc' settings, one of this is DISPLAYMANAGER=console.
This question made me RTFS a little. It seems in 7.3 SuSEconfig doesn't touch the runlevel setting at all. Many thanks to whoever it was that removed it. Now it is possible to have user defined run levels again without having to set CHECK_INITTAB to no.
I'm a little confused by what you're saying here. I would think that CHECK_INITTAB should be set to yes for yast to modify it and indeed that's what it's set o - and it's still not modifying it. Are you saying I need to set it to "no" (that would seem backwards to me)?
Setting DISPLAYMANAGER=console has the same effect as setting it to DonaldDuck, in other words if you're in runlevel 5 you'll get the default display manager, which is xdm.
Weird. On 7.2 and older is used to take care of the runlevel as well.
The runlevel now is only set by YaST internally, by going to System Configuration -> Login and setting "graphical" or "Ascii". Unless you prefer to edit inittab manually, that is.
I don't really care if I do have to set it by hand but I wonder why on earth SuSE messed with something that used to work perfectly fine?
Of course I may have misread the source, but it is verified by experience.
regards Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com
On Wednesday 06 February 2002 22.04, JW wrote:
At 07:03 PM 2/6/2002 +0100, you wrote:
On Wednesday 06 February 2002 18.09, JW wrote:
Hello,
I just made a brand-new installation of 7.3 and one of the first things I did after the install was open yast and set all my favorite 'rc' settings, one of this is DISPLAYMANAGER=console.
This question made me RTFS a little. It seems in 7.3 SuSEconfig doesn't touch the runlevel setting at all. Many thanks to whoever it was that removed it. Now it is possible to have user defined run levels again without having to set CHECK_INITTAB to no.
I'm a little confused by what you're saying here. I would think that CHECK_INITTAB should be set to yes for yast to modify it and indeed that's what it's set o - and it's still not modifying it. Are you saying I need to set it to "no" (that would seem backwards to me)?
No, I was saying that I don't normally want YaST/SuSEconfig to change the runlevel settings on me. in versions up to and including 7.2 it would do this every time SuSEconfig ran, so I habitually set CHECK_INITTAB to no. Your question made me look and found that this behaviour has changed thankfully.
Setting DISPLAYMANAGER=console has the same effect as setting it to DonaldDuck, in other words if you're in runlevel 5 you'll get the default display manager, which is xdm.
Weird. On 7.2 and older is used to take care of the runlevel as well.
Yep. Not anymore.
The runlevel now is only set by YaST internally, by going to System Configuration -> Login and setting "graphical" or "Ascii". Unless you prefer to edit inittab manually, that is.
I don't really care if I do have to set it by hand but I wonder why on earth SuSE messed with something that used to work perfectly fine?
I don't think it worked that well. There was no way to have SuSEconfig run on inittab if you had set up localized run levels. Using runlevel 4 (for instance) to have your own stuff can be useful and you don't have to delete/edit pre-defined runlevels, but it doesn't fit into the "either 5 or 3" philosophy of previous versions. I'm glad it's changed regards Anders
participants (3)
-
Anders Johansson -
JW -
Mark Hounschell