Preventing udev from creating device entries under /dev
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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Preventing udev from creating device entries under /dev
Hi,
I need to prevent udev from creating the /dev/v4l/by-path/* and /dev/v4l/by-id/* files upon connecting my webcam. The problem is that Kopete doesn't want to display the video if these files are present. It works fine if I remove them, but I'd rather not have them created in the first place, since they seem to be completely useless anyway.
The correct place is /lib/udev/rules.d, like catkin suggested (is this distribution dependent?). Removing 60-presistent-v4l.rules file from that directory prevents the /dev/v4l files from being created and the webcam works like charm.
The correct place is /lib/udev/rules.d, like catkin suggested (is this distribution dependent?).
Glad you found a solution
According to the udev man page "The udev rules are read from the files located in the default rules directory /lib/udev/rules.d/, the custom rules directory /etc/udev/rules.d/ and the temporary rules directory /dev/.udev/rules.d/. All rule files are sorted and processed in lexical order, regardless in which of these directories they live". So both locations are correct and neither takes precedence.
It may be that the /lib/udev/rules.d/ is the preferred location for rules created during installation and upgrade while /etc/udev/rules.d/ is the preferred location for local customisation. This theory is based on most of the files in the lib directory on Slackware 13.0 starting with the comment "# do not edit this file, it will be overwritten on update".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.