Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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 was messing with an untested device driver, and now I'm facing the consequences. I'll skip the details of what happened and get to the symptom. This box with Redhat Enterprise 4 used to boot with two HID device files in /dev: hiddev0 and hiddev1. Even when I would mess one of them up, a reboot would restore their original condition. Now I don't get hiddev1. I can create it anew with mknod, but it doesn't seem to work. It doesn't appear in /proc/bus/usb/devices.
There must be something in the boot procedure that cleans up /dev and
creates what needs to be created. So far I haven't been able to find it. Can someone set me straight?
Hardware detection on most systems I've seen lately is done by hotplug. There is a step while booting called "coldplug" which is really just running hotplug to do initial hardware detection (and rededication of previously detected devices)
Doesn't answer your question, but it might help.
Also, it is fun to play in the /sys pseudo file system. This might help prove that the system sees the device at all (even if the driver is wrong). Note that /sys is not always a friendly place, but it is useful. I suggest looking in /sys/bus.
Thanks for the advice. Unfortunately I can't make any progress for a while because of a hardware problem. The device is a Tripp-Lite UPS. It's gone into a funny mode in which it won't talk to the USB port and I can't turn it off or make it self-test. Unplugging it doesn't help because, of course, it has a whopping big battery that will keep it going for a very long time. While messing around with software, I discovered that I was able to shut it off inadvertently. Maybe I did something even worse. Stay tuned.