SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have been using KDE WM for some months but now decided to switch to xFCE mostly because my pc is quite slow and it doesn't perform as well in KDE as it does in xFCE.
First issue : I used xwmconfig and chose xFCE as Default, when I hit startx it works perfectly, however when I reboot right after the start kdm is automatically loaded.
Second issue and most important : I changed the userlevel in my inittab back to 3 and it worked ok but I still wanted xFCE to load automatically so I tried to edit my rc.4 file (big mistake) I tried to comment the lines that detected if kdm was present in my system and all I got was an error saying "can not execute rc.4" and it just stops there.
I editted it, changed it back to how I found it but I am still getting the same error
I can not see anything wrong with it as I tried to leave it exactly as I think it was before but I can not make it.
What I am currently doing at the error is hitting ALT+CTRL F6, log in and manually startx and then it loads xFCE.
I am a progressively learning newbie but I am very lost here. I have tried to search for forums referring to this but it's a hard to look for subject.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
Without the error messages and knowing what you changed, it's hard to know how to fix what is broken in rc.4. Just see if you can download a copy from slackware.com.
You should never default to log into a graphical environment, because if something is broken, you won't be able to log on as root.
I like to set up my user accounts to automatically start x. They each have their own .xinitrc file in the user directory to select a window manager and other apps.
Basically, you just create a file called .bash_profile and from this script, you execute whatever you want. It will be invoked when the user logs in. I have mine symlinked and protected so nobody can mess with it.
Thanks a lot, this is very helpful. I will try to get the specific error message or better yet, try to fix it. I have been browsing for quite a long time now through webpages and distributions but I can not find a way to get the rc.4 file. I have been browsing ftps but I don't know if perhaps these files are not posted or "hidden" among the numerous folders.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
Quote:
Originally Posted by paulocr
Thanks a lot, this is very helpful. I will try to get the specific error message or better yet, try to fix it. I have been browsing for quite a long time now through webpages and distributions but I can not find a way to get the rc.4 file. I have been browsing ftps but I don't know if perhaps these files are not posted or "hidden" among the numerous folders.
And then (do this as user so as not to toast your system) make a directory and untar the package under it. Pull out rc.4 and as root, slap it down over your /etc/rc.d
I've also copied it here, maybe you can save some time.
Code:
#! /bin/sh
#
# rc.4 This file is executed by init(8) when the system is being
# initialized for run level 4 (XDM)
#
# Version: @(#)/etc/rc.d/rc.4 2.00 02/17/93
#
# Author: Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org>
# At least 47% rewritten by: Patrick J. Volkerding <volkerdi@slackware.com>
#
# Tell the viewers what's going to happen...
echo "Starting up X11 session manager..."
# Try to use GNOME's gdm session manager:
if [ -x /usr/bin/gdm ]; then
exec /usr/bin/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
fi
# If all you have is XDM, I guess it will have to do:
if [ -x /usr/X11R6/bin/xdm ]; then
exec /usr/X11R6/bin/xdm -nodaemon
fi
# error
echo
echo "Hey, you don't have KDM, GDM, or XDM. Can't use runlevel 4 without"
echo "one of those installed."
sleep 30
# All done.
I have been using KDE WM for some months but now decided to switch to xFCE mostly because my pc is quite slow and it doesn't perform as well in KDE as it does in xFCE.
First issue : I used xwmconfig and chose xFCE as Default, when I hit startx it works perfectly, however when I reboot right after the start kdm is automatically loaded.
<snip>
Thanks so much,
Paulo.
I just wanted to point out that runlevel 4 booting to KDM is the proper functioning. You will then need to pick XFCE from the list of available window managers/DE's from the sessions dropdown list. Once you have booted to XFCE from KDM, you will automatically log into XFCE as your default windowmanager from KDM once you enter your name and password. At least until you log into something different.
KDM is configurable from the KDE Control Center and with root privilages you can set KDM to automatically boot a specific user to a specific window manger without stopping to ask for a username and password. You can run KDE Control Center from XFCE if needed by running kcontrol from the command line.
System Administration -> Login Manager -> Convenience Tab.
Sorry if you knew this allready, it was not clear.
This is really weird but the file looks exactly like that....Sometimes it ends up trying to execute GDM and it freezes ( since I do not have GDM ) and sometimes the boot just ends up with "Can not execute etc/rc.d/rc.4"...I am able to log in as root if I hit ALT CTRL F6.
Strangest thing is that even if I change the userlevel from 4 to 3 in the inittab it will keep on trying to execute rc.4
Is there a way to reinstall or fix the damaged modules ?
I have looked closely into the rc.4 file and I see no error there, I have also looked at the inittab.
Can I comment the lines trying to execute GDM so that it will go directly to KDM ?
May someone perhaps attach or email me the rc.4 and inittab file of your own so that I can replace it in my pc ?
Randux already posted the rc.4 file all you have to do is copy the text and paste it. As for getting rid of the GDM manager just comment out the lines:
if [ -x /usr/bin/gdm ]; then
exec /usr/bin/gdm -nodaemon
fi
Second issue and most important : I changed the userlevel in my inittab back to 3 and it worked ok but I still wanted xFCE to load automatically so I tried to edit my rc.4 file (big mistake) I tried to comment the lines that detected if kdm was present in my system and all I got was an error saying "can not execute rc.4" and it just stops there.
I editted it, changed it back to how I found it but I am still getting the same error
I can not see anything wrong with it as I tried to leave it exactly as I think it was before but I can not make it.
Sounds like a permission problem to me. Perhaps your rc.4 lost it's execute bit when you edited it? Try:
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
Nice going alienDog!
Just a general note: in Slackware you shouldn't have to comment out portions that execute scripts. Just change the execute permission if you don't want something to run. (the opposite of this problem!)
For example instead of commenting-out this:
if [ -x /usr/bin/gdm ]; then
exec /usr/bin/gdm -nodaemon
fi
Do this:
chmod -x /usr/bin/gdm
Even so, I don't think this is the problem because the script is designed to work if stuff isn't there. That section of code will execute correctly whether or not you have gdm in /usr/bin
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.