-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
udev rules on Arch(-ish) systems #441
Comments
Yes, I'd also suggest adding There's also IIRC Ewen |
One of the issues here is that (Actually, looking at this description it would simply not work unless you relogin to your desktop, which is insane, and so I hope the description is wrong.) I'm going to close this issue because I don't want to deal with broken and undocumented systemd stuff. Anyone who has a demonstrably working solution (which works across OSes and with/without systemd) is welcome to offer a PR updating the udev rules. If the current state of udev rules is unsatisfying (due to missing I've opened #442 to track the addition of |
Looking carefully at Debian's SystemGroups page it seems that our current use of the plugdev group is actually a misuse, since it's not a disk:
What a mess. |
I made some progress in figuring out what went wrong with
With this rules file, the device does get an ACL applied:
but it's still not accessible:
Why? Who knows. |
This error message is terrible, I've fixed it in #442. It now looks like:
Then you can look at |
Scratch all of this; I was looking at the wrong device file, the tags have never worked in first place. |
…`GROUP`. The existing solution with `GROUP="plugdev"`, `MODE="0660"` is Debian specific, and generally such groups are discouraged on modern Linux desktop systems. There is no group for "USB development tool" and we don't want to create one, but `TAG+="uaccess"` works fine for this. We already had `TAG+="uaccess"` but due to a rule ordering issue it did nothing. Move rules from `99-*.rules` to `70-*.rules` to fix this issue and have the tag assign the right ACL on ~most modern Linux desktop systems. Fixes GlasgowEmbedded#441.
Okay, I figured this mess out. It's all in #442. |
…`GROUP`. The existing solution with `GROUP="plugdev"`, `MODE="0660"` is Debian specific, and generally such groups are discouraged on modern Linux desktop systems. There is no group for "USB development tool" and we don't want to create one, but `TAG+="uaccess"` works fine for this. We already had `TAG+="uaccess"` but due to a rule ordering issue it did nothing. Move rules from `99-*.rules` to `70-*.rules` to fix this issue and have the tag assign the right ACL on ~most modern Linux desktop systems. Fixes GlasgowEmbedded#441.
…`GROUP`. The existing solution with `GROUP="plugdev"`, `MODE="0660"` is Debian specific, and generally such groups are discouraged on modern Linux desktop systems. There is no group for "USB development tool" and we don't want to create one, but `TAG+="uaccess"` works fine for this. We already had `TAG+="uaccess"` but due to a rule ordering issue it did nothing. Move rules from `99-*.rules` to `70-*.rules` to fix this issue and have the tag assign the right ACL on ~most modern Linux desktop systems. Fixes GlasgowEmbedded#441.
…`GROUP`. The existing solution with `GROUP="plugdev"`, `MODE="0660"` is Debian specific, and generally such groups are discouraged on modern Linux desktop systems. There is no group for "USB development tool" and we don't want to create one, but `TAG+="uaccess"` works fine for this. We already had `TAG+="uaccess"` but due to a rule ordering issue it did nothing. Move rules from `99-*.rules` to `70-*.rules` to fix this issue and have the tag assign the right ACL on ~most modern Linux desktop systems. Fixes GlasgowEmbedded#441.
…`GROUP`. The existing solution with `GROUP="plugdev"`, `MODE="0660"` is Debian specific, and generally such groups are discouraged on modern Linux desktop systems. There is no group for "USB development tool" and we don't want to create one, but `TAG+="uaccess"` works fine for this. We already had `TAG+="uaccess"` but due to a rule ordering issue it did nothing. Move rules from `99-*.rules` to `70-*.rules` to fix this issue and have the tag assign the right ACL on ~most modern Linux desktop systems. Fixes #441.
Hi,
I've just tried to setup the glasgow on an Arch machine.
The file glasgow/config/99-glasgow.rules uses the plugdev-group, which doesn't exist on Arch.
Possible solutions:
The readme also seems to be missing the
step, as well as a more explicit hint to re-plug the device after this (to apply the new permissions).
The text was updated successfully, but these errors were encountered: