It could be either, but these names are assigned by the kernel – not by
udev.
On Thu, Oct 29, 2020, 22:53 Marcin Kocur wrote:
> Hello,
>
> this is the output of turning off and on my display (using power button):
>
>
> [mk@linux ~]$ udevadm monitor
> monitor will print the received events for:
Hello,
this is the output of turning off and on my display (using power button):
[mk@linux ~]$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[79.909185] change
/devices/pci:00/:
There is a bug with the system upgrade of fedora that
user services run while the system is doing the upgrade.
https://bugzilla.redhat.com/show_bug.cgi?id=1829799
Clearly I do not want to have my user's user services running
when I do the F33 upgrade.
What workaround do you suggest that I use wh
I used to just have to add-wants ssh.service to rescue.target and I
could isolate to rescue mode for remote system maintainence without
loosing remote access to the server. After an upgrade, even though
ssh.service is wanted by rescue.target, it is still killed if I
isolate. How can I figure out
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 an
