Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
well...... I really screwed up this time. I just bought a new Logitech cordless optical USB mouse. I had no trouble installing it and getting SuSe 10 to recognize it. It's been working almost exactly as I wanted it to with the exception of the wheel only scrolling down a page, not back up.
So.......here is where I went wrong. Using KDE, I went into the configure system icon and tried to configure the mouse as another one in the list of Logitech mice. (my new mouse not in the list)
Now I have rebooted my system and the mouse has gone completely mad. I have no control over it and with the slightest movement it's opening up applications, windows all over the desktop..... out of control.
well... I tried the advise, but for the life of me I could not remember the password I thought I had established, so going to CLI was not available. I tried doing it GUI but the mouse was so unstable that since I only had SuSe up and running for a few days I decided to do a complete reinstall.
Little more than some time lost in the process. And a valuable lesson learned.... write the password down somewhere.
Although...... I only remember establishing a SU password, not a user password, and that's what the system was asking me for.
You could go into single user mode which is runlevel 1 by passing the number 1 at the boot loader screen. They type passwd and type a password that you can remember. No, runlevel 1 will not ask for the old password upon boot up.
Microsoft has brain washed you into thinking that re-installing their OS is the only fix. In Linux, there are many ways to skin a mouse.
It is that easy if corresponding configuration file supposes that anyone having physical access can just boot from cd and chroot as root (chroot allows you to work as if you had the root directory in other place - for example, on mounted filesystem). Anyway, physical access means being able to edit hard disk from boot cd, so for ordinary users there is no point in defending against someone in this case.