A very standard and useful rule (/etc/udev/rules.d/99-hide-drives.conf)KERNEL=="sda1", ENV{UDISKS_IGNORE}:="1"KERNEL=="sda2", ENV{UDISKS_IGNORE}:="1"KERNEL=="sda4", ENV{UDISKS_IGNORE}:="1"seems to be completely ignored.
Strike0 wrote:Anyhow, two ways to try alternatively: 2. Use Udev for something similar by creating e.g. /etc/udev/rules.d/70-persistent-net.rulesSUBSYSTEM=="net", ACTION=="add", DRIVERS=="rt2500pci", KERNEL=="wlan0", RUN="/sbin/iwconfig wlan0 power off"Have a go at one at a time.Solution 2 is worked for me.
tesjo wrote:Ok this is not elegant but it is working for me.I created file /etc/udev/rules.d/82-cdrom.rules as follows# Custom CD-ROM symlinks
SUBSYSTEM=="block", KERNEL=="sr0", SYMLINK+="cdrom cdrw dvd dvdrw"I found in my other Gentoo box a /etc/udev/rules.d/70-persistent-cd.rules, which i adapted for this Archlinux machine :SUBSYSTEM=="block", ENV{ID_CDROM
@jrussell: i had a look at this, and it appears that he ssb subsystem in the kernel does not support predictable network interface names. So even if my patch might appear to work, I don't think it will end up being a good idea (as the names might actually end up changing randomly after all).What you could do instead, would be to use the macadress.
Okay, nevermind. The first time I looked over 70-uaccess.rules, I skipped over the relevent line. Here it is in all its glory # DRI video devices
SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess"
WonderWoofy
https://bbs.archlinux.org/profile.php?id=60312
2012-10-29T04:27:19Z
How about the nice & simple:KERNEL=="lp*", DRIVERS=="usblp", GROUP="lp", MODE="664"
brebs
https://bbs.archlinux.org/profile.php?id=10353
2013-02-12T10:01:39Z
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.
@cfr, I think this: # optical drives
SUBSYSTEM=="block", ENV{ID_CDROM}=="1", TAG+="uaccess"
SUBSYSTEM=="scsi_generic", SUBSYSTEMS=="scsi", ATTRS{type}=="4|5", TAG+="uaccess"is supposed to give you access...
Just a quick thanks that it worked, aesiris.Also on the that page: https://wiki.archlinux.org/index.php/Po … Managementi2c device power management can be managed with very much the same rule structure:ACTION=="add", SUBSYSTEM=="i2c", TEST=="power/control", ATTR{power/control}="auto"Can't for sure say the same for spi devices, since I apparently ha
Email this page
