From 342a404f2a09afd6c957116052f15fc99ce4de27 Mon Sep 17 00:00:00 2001

From: Lennart Poettering <lennart@poettering.net>

Date: Wed, 16 Oct 2013 02:49:54 +0200

Subject: [PATCH] rules: expose loop block devices to systemd

Since the kernel no longer exposes a large number of "dead" loop devices

it is OK to expose them now in systemd, so let's do that. This has the

benefit that mount dependencies on loop devices start to work.

---

 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 bbb7d0c..3c99475 100644

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

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

@@ -11,12 +11,12 @@ SUBSYSTEM=="tty", KERNEL=="tty[a-zA-Z]*|hvc*|xvc*|hvsi*", TAG+="systemd"

 KERNEL=="vport*", TAG+="systemd"

-SUBSYSTEM=="block", KERNEL!="ram*|loop*", TAG+="systemd"

-SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"

+SUBSYSTEM=="block", KERNEL!="ram*", TAG+="systemd"

+SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_UDEV_DISABLE_OTHER_RULES_FLAG}=="1", ENV{SYSTEMD_READY}="0"

 # Ignore encrypted devices with no identified superblock on it, since

 # we are probably still calling mke2fs or mkswap on it.

-SUBSYSTEM=="block", KERNEL!="ram*|loop*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"

+SUBSYSTEM=="block", KERNEL!="ram*", ENV{DM_UUID}=="CRYPT-*", ENV{ID_PART_TABLE_TYPE}=="", ENV{ID_FS_USAGE}=="", ENV{SYSTEMD_READY}="0"

 # Ignore raid devices that are not yet assembled and started

 SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", KERNEL=="md*", TEST!="md/array_state", ENV{SYSTEMD_READY}="0"