SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a weird problem I have never seen before:
I finally have been able to set up X and it's working - great. However, if I shut it down, the mouse is still visible, like a console mouse. I can move it, but it only does weird stuff like marking lines, and from time to time bash gives me an error, but always a different one ... one I remember was that I should turn off X security features
Now, I got the following output from bash when moving the mouse:
(++) from command line, (!!) notice, (II) informational, (++) from command line, (startx) notice, (II) informational,
bash: syntax error near unexpected token 'from'
Any idea how much alcohol my PC has gotten
Thanks for your help
i wouldn't advise changing those permissions, jsut seems like pulling the carpet out from underneath it, not nice i don't think. you should instead remove the command to start the service in the first palce from your /etc/rc.d/rc3.d directory instead, that way the gpm script will never be called in the first place, rather than just forcing it to fail. this is what teh sysvinit system would do anyway, so you could just save confusin and remove it by hand.
The rc.gpm script is called from the rc.M script. The rc.M script checks for the execute bit to be set before attempting to run it. Clearing the exec bit allows the script to be cancelled without any modifications to the scripts. ( if [ -x /etc/rc.d/rc.gpm ]; then) Most all of the startup scripts are written in this manner to support this operation.
The chmod on the gpm program itself was more of a last resort. I do not suspect it to be required. Only used if the original start code can not be easily determined, like in the stupid sysvinit system. I only added as a "just in case."
Well, it worked - I just commented everything in rc.gpm - the file isn't too large so it's not a problem.
In the script was also written, that gpm could cause problems if used together with X - that's what happened.
If you want the ability to copy text in a console without using a mouse, try running the screen command. You can copy text in the window or you can copy to other windows.
With the screen command, you can open other windows. I think up to ten windows. It's like logging in to the other consoles, but in this case you only use one console screen. Read the man page for screen.