Lennart Poettering
Lennart Poettering
> Yes. There might be devices for which CHIDs are different (i.e. different SKUs) but the hardware is the same. So every such SKU will have to be upstreamed to...
> Yes, they are. So consider the following scenario: > > 1. Upstream DT was sent only with CHIDs for SKU A (because this is what DT author had) and...
If there's no sane way to check for the feature explicitly I figure we could query the fuse minor version FUSE_KERNEL_MINOR_VERSION) from the device and base things on that.
(i.e. the point i am making, if we have to do a version check, then it should be a runtime hceck against the fuse version, and not the kernel. i.e....
oh, yes, please. well, sha384 is part of the standard, it's just a lot less often used IRL
I am not convinced that that would be a good idea. In particular as network.target has no meaning at all during boot-up, it only has an effect on shutdown: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/...
for the network-online case I think it would make more sense to just provide systemd-networkd-wait-online.service also as a user session
hmm, but that means we turn off session switching for logitech devices, which sounds like quite a major security issue...
it appears to me we should revisit this whole uaccess thing on hidraw thing and maybe go another way: add a dbus api to logind to open these for clients....
> But do note that this is already a problem for anyone using the Solaar Logitech receiver management app that allows things like pairing and unpairing devices from the receiver:...