On 2014-09-25, Mike Gilbert <[email protected]> wrote: > On Thu, Sep 25, 2014 at 11:28 AM, Grant Edwards ><[email protected]> wrote: >> On 2014-09-25, Mike Gilbert <[email protected]> wrote: >>> On Wed, Sep 24, 2014 at 6:28 PM, Grant Edwards >>><[email protected]> wrote: >>>> On 2014-09-24, Neil Bothwick <[email protected]> wrote: >>>>> On Wed, 24 Sep 2014 19:42:56 +0000 (UTC), Grant Edwards wrote: >>>>> >>>>>> After an update yesterday, I've noticed that the group assigned to >>>>>> ttyUSB devices has changed from uucp to root. Non-USB serial ports >>>>>> still seem to be uucp. >>>>> >>>>> What did you update? They are still root:uucp here. >>>> >>>> Several things got updated, but the most likely suspect is probably >>>> sys-fs/udev-215-r1 => sys-fs/udev-216. But, I don't see any changes >>>> in the default rules to account for the change in behavior. >>> >>> I'm running systemd-216, and I see this in >>> /lib/udev/rules.d/50-udev-default.rules: >>> >>> KERNEL=="tty[A-Z]*[0-9]|pppox[0-9]*|ircomm[0-9]*|noz[0-9]*|rfcomm[0-9]*", >>> GROUP="uucp"
The test trace shows that rule setting the group to 14 (uucp). >>> I suppose it is possible that some later rule overrides it, but I >>> don't see anything obvious. It appears to be overridden by /lib64/udev/rules.d/99-openocd.rules Which sets the group to 0 (root). The weird thing is that I don't know where that file came from. Dong an "equery belongs" doesn't show it belonging to any package. I do have dev-embedded/openocd installed, but it doesn't own that file... But, doing an emerge -C openocd removed the file /lib64/udev/rules.d/99-openocd.rules. It looks like a bug in the openOCD rules is causing it to recognize somthing that it shouldn't. Checking the emerge logs shows that openocd was emerged about a week prior to the udev update (and I must have been mistaken about exactly when the failure started). -- Grant
