adding graphical login

[NorMan-drake9]

OK I've done the search in JL and tabed through about ten pages and no results.

When I installed RH8 I unchecked the graphical login button and clicked on finish too fast. Now I am stuck with startx, which is fine for me but not for my wife. I downloaded XD2 (and was hoping that that might fix it, but it didn't) what do I need to do to get back to login screen at start up?


ThanX,

Norm

[ph34r]

edit /etc/inittab and change teh default runlevel from 3 to 5.

[dysharmonic]

id:3:initdefault:

Change 3 to 5.

[NorMan-drake9]

Thanks for the speedy reply.

I opened up /etc/inittab and this is what it reads


#
# inittab This file describes how the INIT process should set up
# the system in a certain run-level.
#
# Author: Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
# Modified for RHS Linux by Marc Ewing and Donnie Barnes
#

# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
#
id:3:initdefault:

# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Things to run in every runlevel.
ud::once:/sbin/update

# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"


# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

# Run xdm in runlevel 5
# xdm is now a separate service
x:5:respawn:/etc/X11/prefdm -nodaemon #<====This is the only mention of X that I see --Norm#

[NorMan-drake9]

I see the id:3:inittab I'm changing it.

[NorMan-drake9]

That don't work. Now when I reboot it hangs on rcd. I think I am misunderstanding the whole id:5:inittab thing.

[mdwatts]

Why not just restart the installation (boot from cd), select expert, select upgrade and then select the required packages such as KDE/KDM (graphical logon) etc. that you are missing.

Redhat should have docs on their site on adding packages after installation.

[NorMan-drake9]

Well I decided to reinstall the OS (for good measure). This morning while drinking my coffee it hit me why rcd hung on the reboot. It had nothing to do with changing id:3 . I am playing around with PXES and had added /usr/sbin/in.tftpd to my rc.local file. I left out the -l option that starts the tftpd in listen mode, hence when it processed rcd it just starded the tftpd and never put it in the background.

mdwatts, that would be a great quick fix? And no doubt it would work. However what would I learn from doing that? I feel that each time I run into a problem and at least atempt to correct the problem by editing something or starting something, that adds to my knowledge fo how it all comes together. Doing what i did was a last resort and since this is experimental, wiping the OS and starting clean is an option. However, my hope is to one day be a Linux System Admin. in which case it would not be an option.

Thanks for all the help.

Norm