From 9a3296571683a6a3eaee44d18db91ca113841da6 Mon Sep 17 00:00:00 2001

From: Lennart Poettering <lennart@poettering.net>

Date: Wed, 16 Oct 2013 02:51:24 +0200

Subject: [PATCH] rules: don't limit some of the rules to the "add" action

Devices should show up in systemd regardless whether the user invoked

"udevadm trigger" or not. Before this change some devices might have

suddenly disappeared due issuing that command.

Conflicts:

	rules/99-systemd.rules.in

---

 rules/99-systemd.rules.in | 6 +++---

 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in

index 3c99475..307f18f 100644

--- a/rules/99-systemd.rules.in

+++ b/rules/99-systemd.rules.in

@@ -53,12 +53,12 @@ ACTION=="add", SUBSYSTEM=="net", KERNEL!="lo", RUN+="@rootlibexecdir@/systemd-sy

 # Pull in backlight save/restore for all firmware backlight devices

-ACTION=="add", SUBSYSTEM=="backlight", ATTR{type}=="firmware", TAG+="systemd", ENV{SYSTEMD_WANTS}+="systemd-backlight@$name.service"

+SUBSYSTEM=="backlight", ATTR{type}=="firmware", TAG+="systemd", ENV{SYSTEMD_WANTS}+="systemd-backlight@$name.service"

 # Asynchronously mount file systems implemented by these modules as

 # soon as they are loaded.

-SUBSYSTEM=="module", KERNEL=="fuse", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-fs-fuse-connections.mount"

-SUBSYSTEM=="module", KERNEL=="configfs", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-kernel-config.mount"

+SUBSYSTEM=="module", KERNEL=="fuse", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-fs-fuse-connections.mount"

+SUBSYSTEM=="module", KERNEL=="configfs", TAG+="systemd", ENV{SYSTEMD_WANTS}+="sys-kernel-config.mount"

 LABEL="systemd_end"