I've created a udev rule at /etc/udev/rules.d/81-zte.rules with the following:SUBSYSTEMS=="usb", ATTRS{product}=="ZTE HSUSB Device", KERNEL=="sd?1", NAME="%k", SYMLINK+="zte", GROUP="storage", RUN+="/home/afulm/.scripts/zte.sh"It works except that it for some reason refuses to run my script.
I need a udev rule so that it should detect the vendor of the USB pendrive, and allow only specific vendors, rejecting all others.
How to write such a rule ?
Where should the rules be placed /etc/udev/rules.d or /lib/udev/rules.d/
What is the command to get effect of the udev rule.
urgent plz
djgera wrote:Just create a udev rule for such device.Run# udevadm info --attribute-walk -n /dev/bus/usb/006/002Look in the first device (this is your fingerprint) for these lines: ATTR{idVendor} and ATTR{idProduct}Then write a quick and dirty(*) udev rule for it (replace VVVV and PPPP with your numbers)# echo 'ATTR{idVendor}=="VVVV", ATTR{idProduct}=="PPPP", TAG+="ude
i need a udev rule so that it should detect specific vendor and other pendrives it should not allow. how to write a rule and where we have to write the rule is it in /etc/udev/rules.d or /lib/udev/rules.d/ and what is the command to get effect of the udev rule.
urgent plz
i need a udev rule so that it should detect specific vendor and other pendrives it should not allow. how to write a rule and where we have to write the rule is it in /etc/udev/rules.d or /lib/udev/rules.d/ and what is the command to get effect of the udev rule.
I'm forced to work with a bunch of point-of-sale systems running SuSE 8. They are my client's computers. We are stuck dealing with these old systems until they get to upgrade their whole fleet to SLE 11.
The problem: the system now has two devices that compete for the ttyUSB* character device nodes. They have different vendor ID and product ID.
Can anyone explain what files control the udev device mapping. I'm trying to get a fresh install of 11.3 to sync a palm pilot with jpilot.
I have created a "10-pilot.rules " file in /etc/udev/rules.d containing:
udev is responsible for populating /dev. It adds and removes device nodes to /dev dynamically based on rules/configs/scripts under /lib/udev and /etc/udev/.
If I have a CDROM device node /dev/sr0 I can add a symlink /dev/cdrom by adding a rule like:
SUBSYSTEM=="block", KERNEL=="sr0", SYMLINK+="cdrom", GROUP="cdrom"
I understand how symlinks are created in udev.
I have two usb-webcams on them machine, but at bot they some switch /dev/video number.
The solution to this problem seems to be new udev rule.
Email this page
