Slackware

returnzero · 06-11-2009, 03:41 PM

I'm getting a little frustrated at this and would appreciate any help.

First off, when I try to edit Xterm for like colors and stuff, there is suppose to be a hidden /.Xresources , however there isn't, I also can't find the /.Xsessions file as root.

And, as far as I understand. KDM is like a login manager, so when I'm at the initial command line after logging in, i type "kdm" and nothing happens.

Startx starts KDE however, but no KDM.

Also, where is the .xinitrc file located on slackware 12.2 ?? I tried use "locate" as root, but yet another problem appears

Code:

locate: fatal error: Could not find user database '/var/lib/slocate/slocate.db':  No such file or directory

Ahhhhh

msadiq · 06-11-2009, 05:57 PM

Hi,

1. The KDE and the KDM are different. KDE is the desktop environment, whereas KDM is the Display Manager, which is used to present you an artistic login screen.
Since by the time you give the command 'startx' you are already logged in, there is no point in starting KDM.
Try incorporating a startx command in the startup scripts for Runlevel 5.
KDM becomes functional with appropriate runlevel scripts, so you need to tamper a bit there. Most distros have their post install scripts make the necessary changes to Runlevel 5 scripts when KDM package gets installed. Slackware wants you to do it manually - so that you understand how these things work.

2. There are two ways to find files in Linux:
a) Using find
Find searches a directory and all its subdirectories for matches - so a fresh disk read takes place making the search slower for larger filesystems (with more used inodes).
b) Using locate
Locate instead creates a database of the existing files in a neat format so that searching of files can take place by searching the database instead of searching the entire filesystem.
This makes locate really fast but it can't locate files which were created AFTER the last time the database was updated. (Usually locate database is updated at every reboot or every day).

The error you are getting is obvious - the database doesn't exist. To create it type the command 'updatedb' - it may take some time to finish. Once it completes, you may be able to use locate.

Make sure you keep a boot up script to updatedb or you set-up a cronjob to run the updatedb command on a daily basis.

3. Your path for .xinitrc and .Xsessions is nor correct. They are in the respective user's home directory, so its always ~/.xinitrc and ~/.Xsessions.

Note that if .xinitrc doesn't exist in your home directory, the X server will use the default configuration file located at /etc/X11/xinit/xinitrc or someplace like that.

Hope this helps.

metrofox · 06-11-2009, 05:58 PM

If you wanna start KDM you've to edit the /etc/inittab and setting:

Code:

# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:

As you can see in the last string there must be the 4...Once you'll have to edit the /etc/rc.d/rc.4, comment all strings leaving the KDM's strings free.

Code:

#if [ -x /usr/bin/gdm ]; then
#  exec /usr/bin/gdm -nodaemon
#fi

# Someone thought that gdm looked prettier in /usr/sbin,
# so look there, too:
#if [ -x /usr/sbin/gdm ]; then
#  exec /usr/sbin/gdm -nodaemon
#fi

# Not there?  OK, try to use KDE's kdm session manager:
if [ -x /opt/kde/bin/kdm ]; then
  exec /opt/kde/bin/kdm -nodaemon
elif [ -x /usr/bin/kdm ]; then
  exec /usr/bin/kdm -nodaemon
fi

# If all you have is XDM, I guess it will have to do:
#if [ -x /usr/bin/xdm ]; then
#  exec /usr/bin/xdm -nodaemon
#elif [ -x /usr/X11R6/bin/xdm ]; then
#  exec /usr/X11R6/bin/xdm -nodaemon
#fi

returnzero · 06-13-2009, 11:55 AM

Ah, thank you both.

Answered my questions and then some. =)