From f6f738db7273f8a2092ac372852f37f2a34cea17 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Mon, 14 Oct 2013 18:52:07 +0200 Subject: rfkill: use ID_PATH as identifier for rfkill state files Let's include the stable device path for the rfkill devices in the name of the file we store the rfkill state in, so that we have some stability regarding enumeration order. --- rules/99-systemd.rules.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'rules') diff --git a/rules/99-systemd.rules.in b/rules/99-systemd.rules.in index 2ffe744413..8e877809a2 100644 --- a/rules/99-systemd.rules.in +++ b/rules/99-systemd.rules.in @@ -59,7 +59,7 @@ ACTION=="add", SUBSYSTEM=="leds", KERNEL=="*kbd_backlight", TAG+="systemd", ENV{ # Pull in rfkill save/restore for all rfkill devices -ACTION=="add", SUBSYSTEM=="rfkill", TAG+="systemd", ENV{SYSTEMD_WANTS}+="systemd-rfkill@rfkill:$name.service" +ACTION=="add", SUBSYSTEM=="rfkill", TAG+="systemd", IMPORT{builtin}="path_id", ENV{SYSTEMD_WANTS}+="systemd-rfkill@$name.service" # Asynchronously mount file systems implemented by these modules as # soon as they are loaded. -- cgit v1.2.3-54-g00ecf