Installing KDM instead of GDM.
After a fresh install of Slackware 12 onto Nitrogen, the system would not boot via KDM. So I installed KDM on my system and that was it: nothing changed! So now I needed to find a way to get it running.
Step 1 : get some help
My friend Maarten Blomme gave me a tip:
On Slackware: edit /etc/inittab and change default runlevel (or something similar) to '4' (graphic mode, multi-user). To get KDE log in automatically you need to edit kdmrc.conf.This was a start.
Step 2 : do it my way
I found out that the file 'rc4.d' contains the full startup code for the xdm, kdm and gdm software. I just didn't know how to get rc4.d loaded and interpreted upon. But why not do it the easy way? So now the last line in my '/etc/rc.d/rc.local' file reads:
/usr/bin/kdm -nodaemonAnd that seems to do the trick!
Step 3 : friendly intervention
My friend read along with my doings and he strongly advised me to reconsider my deeds:
It may as well work, but the only correct method is to have it in '/etc/inittab' by changing the runlevel.<Grumble>
Of course I need to do things the official way. We're not fooling around with TOS here.
Step 4 : do it right
I checked my trusty old Debian Sarge system (on Beryllium, this PC) and the file '/etc/inittab' contained a lot of text of which this bore some relevance:
# The default runlevel. id:2:initdefault:Now, Beryllium is 100% graphical during boot time. So I guess this line is worth a try. I will change the corresponding line on Nitrogen into
# The default runlevel. id:4:initdefault:I prefer to stick to the rules. Those systems are rather complex and an error is easily made (but very hard to find). On the other hand, my 'kdm in rc.local' trick was also published on a Red Hat forum. Still, Red Hat comes rather close to The Other System.
Step 5 : Is it right?
Yes it is! The system boots right into KDM and then the users can log in. A big hand to all of us.
Page created on 5 November 2008 and
Page equipped with FroogleBuster technology