Mailinglist Archive: opensuse (2886 mails)
| < Previous | Next > |
Re: [SLE] Fried SuSEconfig or yast in 7.3?
- From: Anders Johansson <andjoh@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 6 Feb 2002 22:36:10 +0100
- Message-id: <200202062136.g16LaBh08751@xxxxxxxxxxxxxxxxxxxxx>
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
> 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
| < Previous | Next > |