udev-116-i486-1 and no access to camera with gtkam
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.
At this point, I don't know if udev or the other software is at fault (or perhaps the way udev is configured in -current, although that's not likely since we're now using pretty much a vanilla upstream configuration). PiterPunk is really the resident udev expert - I just put on a good act - so hopefully this will be figured out sooner rather than later. We're on good terms with the udev maintainers in a few other distributions, and I think we've all been working on 116 together for the most part, so we'll check with them tomorrow and see if they've gotten similar reports.
In the meantime, have a look at that other thread as mentioned above. In it, I mentioned a "udevinfo" command and PiterPunk mentioned creating a tarball of various files. Adjust the udevinfo line's device name as appropriate, and send those to us, please -- piterpunk@ and CC to rworkman@