Commit c2f40e58 authored by Johannes Schilling's avatar Johannes Schilling
Browse files

udev rules: remove ACTION=add

we start a udevadm trigger run somewhen after boot, which doesn't run
rules with ACTION=add but instead ACTION=change. that way our rule would
no longer match, and our device would be chowned away. now we always
match and keep our usb device :-)
parent ab1af205
# VOTI shared USB ID, foxtemp benutzt die
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="16c0", ATTR{idProduct}=="05dc", ATTR{product}=="ds1820tousb", MODE:="0660", OWNER:="foxtemp", GROUP:="root"
SUBSYSTEM=="usb", ATTR{idVendor}=="16c0", ATTR{idProduct}=="05dc", ATTR{product}=="ds1820tousb", MODE:="0660", OWNER:="foxtemp", GROUP:="root"
cip-foxtemp (13) stretch; urgency=medium
* final fix for udev permission problem
-- Johannes Schilling <johannes.schilling@cs.fau.de> Thu, 23 Nov 2017 02:06:51 +0100
cip-foxtemp (12) stretch; urgency=medium
* try to correctly fix bootup permission problem
......
cip-foxtemp-hostsoftware usr/sbin
cip-foxtemp-hostsoftware.service lib/systemd/system
70-cip-foxtemp.rules etc/udev/rules.d
70-cip-foxtemp.rules lib/udev/rules.d
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment