Brian T. Schellenberger wrote:
>
> If that's the case, then why does deleting that line solve the problem?
>
> On Thu, 06 Apr 2000, you wrote:
> | For what it's worth, you'll need the line in inittab for X to start in
> | runlevel 5. If you start in runlevel 3, that line is never run, so it's not
> | part of the problem.
> |
> | Russ
> |
> | -----Original Message-----
> | From: [EMAIL PROTECTED]
> | [mailto:[EMAIL PROTECTED]]On Behalf Of Lane Lester
> | Sent: Thursday, April 06, 2000 4:03 AM
> | To: [EMAIL PROTECTED]
> | Subject: Re: [expert] Can't Break X Autostart
> |
> |
> | Brian T. Schellenberger said:
> | > I believe that the reason you get a totally blank screen when you just
> | > do a startx is because you have an empty .xinitrc.
> | >
> | > Since you have a .xinitrc the system one dosn't run 'cause it thinks
> | > you want to replace it with your own, but yours doesn't do anything.
> | >
> | > Thus a plain gray screen.
> | >
> | > Try deleting it and then do a startx.
> |
> | Many, many thanks to you and Civileme and others for sticking with this
> | investigation. It looks like the above finally did the trick. Deleting
> | (well, actually renaming) the .xinitrc and taking out
> | "x:5:respawn:/etc/X11/prefdm -nodaemon" from the bottom of inittab
> | allowed the boot to stop at the console screen and for "startx" to
> | operate without crashing back to the console.
> |
> | Interestingly, now that I've done a startx, the window manager that is
> | running is KDE, not my preferred and previous IceWM. I think I can find
> | where that is going on and make the change.
> | --
> | Lane
> | ____
> | Lane Lester / Madison County, Georgia USA
> | Using Linux to get where I want to go...
> --
> "Brian, the man from babbleon-on" [EMAIL PROTECTED]
> Brian T. Schellenberger http://www.babbleon.org
> Support http://www.eff.org. Support decss defendents.
> Support http://www.programming-freedom.org. Boycott amazon.com.
>
>
>
Deleting the line changes the X behavior--basically breaking it.
I finally reproduced the problem.
High security
user login
su'ed in a Konsole
Set /etc/inittab line to
id:3:initdefault:
logged out and rebooted--finding myself in X
cat /var/run/runlevel.dir
/etc/rc.d/rc5.d
kudzu looks at /etc/inittab and boots to RL5 if it sees 5
linuxconf is called by a symlink called /sbin/askrunlevel and looks in
/var/run/runlevel.dir
Apparently su-ing in High security level enables the permission to edit
a file but not to make linuxconf do its thing.....
So they are out of sync and runlevel 5 is a logical OR of their
individual directives.
It appears the remedy is to use linuxconf to set your runlevel--under
Misc Servives on the opening screen.
Civileme
