Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • Thanks @meuh. That made sense at first. But then remember that 10-local.rules is the only file in /etc/udev/rules.d/ so it may not matter what I rename it to be. However, I am going to try to rename it to something like a 99zzz.rules an dplace it in /lib/udev/rules.d/ in the odd event that ENV{} is being worked upon there and will come back with finding. Commented Oct 8, 2016 at 19:09
  • It worked when I put my new file in /lib/udev/rules.d as the file that is executed last in sequence! Thanks @meuh for the idea. Commented Oct 8, 2016 at 19:20
  • The files in /etc/udev/rules.d/ and /usr/lib/udev/rules.d/ are merged by order of filename, so normally local changes are made in /etc/udev/rules.d/. Commented Oct 8, 2016 at 19:41
  • I am trying to detect USB insert regardless of the device it is. Eg: A phone, a battery pack, a biometric system etc.. which may or may not be recognized by Linux (no drivers or nothing to "Drive/run") Linux will, detect the USB insert, and then proceed to register and act on Recognized devices. For instance it will list USB device details in /dev/bus/usb/ etc... I would like to trap/process everything that is inserted into USB. This means, no dependence on stuff like udevadm. Also means I will need to trap the insert event early on the curve. How do I do this? Commented Oct 9, 2016 at 2:53
  • The one above is a new question, which I was wondering if I could get some on :) Pardon the super terse language, had a character count limitation. lol! Commented Oct 9, 2016 at 2:59