udev.rules documentation improvement #326
No reviewers
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi!326
Loading…
Reference in a new issue
No description provided.
Delete branch "doc-upd"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As recently discovered (thanks @tresf), the
TAG+="uaccess"has to be usedbefore
73-seat-late.rulesand not before70-uaccess.rules.Technically it doesn't harm, to have a more restrictive recommenration,
but it was not technically currect.
Refference on
uaccessTAG consumption:1, 2.
Relates to: #276, systemd/systemd/issues/4288.
@ -21,2 +22,4 @@# https://github.com/systemd/systemd/issues/4288#issuecomment-348166161)# for example, name the file /etc/udev/rules.d/70-my-application-hid.rules.# Then, replug your device or run:# sudo udevadm control --reload-rules && sudo udevadm triggerHow about renaming the file to
72-hid.rules?I tested changing the priority of Mixxx's udev rule file and confirmed this is correct.
@ -21,2 +22,4 @@# https://github.com/systemd/systemd/issues/4288#issuecomment-348166161)# for example, name the file /etc/udev/rules.d/70-my-application-hid.rules.# Then, replug your device or run:# sudo udevadm control --reload-rules && sudo udevadm triggerSo there is a standard set of rules that adds a
uaccessTAG (70-uaccess.rules) with priority70.I'm thinking maybe having and example with the same priority would be nit.
Looks good to me!