On Thu, Dec 29, 2016 at 01:54:52AM +0000, Martin Ling wrote: > On Wed, Dec 28, 2016 at 11:49:50AM +0300, Paul Fertser wrote: > > > > So what libsigrok usecase on what particular OS won't be covered by > > doing all three of these: > > > > 1. plugdev group assignment > > 2. uaccess tag > > 3. ModemManager antidote? > > Apparently this wouldn't be acceptable on Fedora - they wanted uaccess > only. That was what led to the discussion in our bug #665.
But here we are not talking about providing udev rules that can be distributed by Fedora in their official RPM. We are talking about providing some default (example) udev rules that should work on (almost ?) all linux distro using udev, for users building sigrok themselves, so they can get up and running as easily as possible. And from the bug repport and various other linked repports, I see no hints that GROUP="plugdev" would prevent the uaccess tag to work on Fedora. It may only print a warning that the plugdev group doesn't exist. So I think the proposed solution to have an example udev rules file with both plugdev group and uaccess tag is a good and simple solution that should work fine in pretty much all situations. Aurel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
