[systemd-devel] Non-idempotent RUN+= scripts

2025-10-17 Thread Demi Marie Obenour
There are cases where a RUN+= script needs to do something exactly once each time a device appears, such as binding a different driver to the device. If the udev rule matches based on a property (such as PCI device information) that is set only by the kernel, is it okay to use ACTION=="add" in the

Re: [systemd-devel] Non-idempotent RUN+= scripts

2025-10-17 Thread Mantas Mikulėnas
On Wed, Sep 24, 2025 at 8:27 PM Demi Marie Obenour wrote: > There are cases where a RUN+= script needs to do something > exactly once each time a device appears, such as binding a > different driver to the device. If the udev rule matches > based on a property (such as PCI device information) th

Re: [systemd-devel] Non-idempotent RUN+= scripts

2025-09-24 Thread Andrei Borzenkov
24.09.2025 23:46, Demi Marie Obenour wrote: On 9/24/25 13:46, Mantas Mikulėnas wrote: On Wed, Sep 24, 2025 at 8:27 PM Demi Marie Obenour wrote: There are cases where a RUN+= script needs to do something exactly once each time a device appears, such as binding a different driver to the device.

Re: [systemd-devel] Non-idempotent RUN+= scripts

2025-09-24 Thread Demi Marie Obenour
On 9/24/25 13:46, Mantas Mikulėnas wrote: > On Wed, Sep 24, 2025 at 8:27 PM Demi Marie Obenour > wrote: > >> There are cases where a RUN+= script needs to do something >> exactly once each time a device appears, such as binding a >> different driver to the device. If the udev rule matches >> bas