Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Having not messed with desktop Linux for a little while, I'm a little stuck trying to disable a touchpad on a new Thinkpad. I can use xinput to disable it for about 20 seconds, but something seems to time out and reenable it. What would be doing that? hal? Xorg? the synaptic driver? Additionally, what is the most formal way to make this persist with the lack of persitent xorg.conf files?
Well the point (ba dum tish!) is that now there is no xorg.conf by default, I have no idea where this would be formally set. That's half the query, but also why it seems to disable for about 20 seconds with some tools and then leap back into live, as if hal flushes out settings or something.
Ahh, I think I sussed it finally. So disabling the mouse on typing, which is all you can do with the fedora mouse settings tool, means that on key press the disable command is triggered by the syndaemon tool, but then after the timeout the enable command is sent to reenable the touchpad. So if that option is on AND you try and permanently disable it using other methods, then it will be reenabled regardless when that enable comes through. So by unchecking the option to disable whilst typing, it can be permanently disabled. Wonder if that's worth a bug report, as it's fscking confusing to me at least. Thanks for the pointers guys.