Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-30 Thread Lennart Poettering
On Do, 29.10.20 17:55, Marcin Kocur (marcin2...@gmail.com) wrote: > W dniu 26.10.2020 o 11:19, Lennart Poettering pisze: > > > Is this intended? Should I report bug to systemd or sane? The scanner is > > > connected to my PC all the time. > > sane. > > > > Ask them to run their rules on

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-29 Thread Marcin Kocur
W dniu 26.10.2020 o 11:19, Lennart Poettering pisze: Is this intended? Should I report bug to systemd or sane? The scanner is connected to my PC all the time. sane. Ask them to run their rules on ACTION!="remove", i.e. on all actions but "remove". And that includes add, bind, change, unbding

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-26 Thread Marcin Kocur
W dniu 26.10.2020 o 11:19, Lennart Poettering pisze: On So, 25.10.20 18:56, Marcin Kocur (marcin2...@gmail.com) wrote: W dniu 25.10.2020 o 18:36, Marcin Kocur pisze: Hello, as the topic states, I want to know which action(s) from "add", "remove", "change", "move", "online", "offline",

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-26 Thread Lennart Poettering
On Mo, 26.10.20 11:28, Pekka Paalanen (ppaala...@gmail.com) wrote: > > So the ultimate quesiton is: what kind of trigger was executed on my > > device on boot time? > > > > Hi, > > FWIW, I was totally baffled by a similar problem with a DRM device. My > rule was doing the same thing: match to

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-26 Thread Lennart Poettering
On So, 25.10.20 18:56, Marcin Kocur (marcin2...@gmail.com) wrote: > W dniu 25.10.2020 o 18:36, Marcin Kocur pisze: > > Hello, > > > > as the topic states, I want to know which action(s) from "add", > > "remove", "change", "move", "online", "offline", "bind", and "unbind" > > were triggered on my

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-26 Thread Lennart Poettering
On So, 25.10.20 18:36, Marcin Kocur (marcin2...@gmail.com) wrote: > Hello, > > as the topic states, I want to know which action(s) from "add", "remove", > "change", "move", "online", "offline", "bind", and "unbind" were triggered > on my device. Is there any way to check that? > > At the

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-26 Thread Pekka Paalanen
On Sun, 25 Oct 2020 18:36:42 +0100 Marcin Kocur wrote: > Hello, > > as the topic states, I want to know which action(s) from "add", > "remove", "change", "move", "online", "offline", "bind", and "unbind" > were triggered on my device. Is there any way to check that? > > At the beginning of 

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-25 Thread Marcin Kocur
W dniu 25.10.2020 o 18:36, Marcin Kocur pisze: Hello, as the topic states, I want to know which action(s) from "add", "remove", "change", "move", "online", "offline", "bind", and "unbind" were triggered on my device. Is there any way to check that? At the beginning of 

Re: [systemd-devel] Which udev action is run on boot for my device?

2020-10-25 Thread Andrei Borzenkov
25.10.2020 20:36, Marcin Kocur пишет: > Hello, > > as the topic states, I want to know which action(s) from "add", > "remove", "change", "move", "online", "offline", "bind", and "unbind" > were triggered on my device. Is there any way to check that? > > At the beginning of 

[systemd-devel] Which udev action is run on boot for my device?

2020-10-25 Thread Marcin Kocur
Hello, as the topic states, I want to know which action(s) from "add", "remove", "change", "move", "online", "offline", "bind", and "unbind" were triggered on my device. Is there any way to check that? At the beginning of  /usr/lib/udev/rules.d/49-sane.rules there is: ACTION!="add",