[arch-projects] [PATCH 07/10] workaround: do not set property=STARTUP=1 when calling udevadm

[Tom Gundersen]

This was needed to properly deal with dm devices being created in
initrd. However, the lvm2/devicemapper rule files no longer use this
property and now contain a proper fix.

By grepping through /lib/udev/rules.d I could not find any other rule
file using this property. Finally, the startup script submitted to
systemd by the udev maintainer does not set the property, and there has
not been any bug complaints about this.

Signed-off-by: Tom Gundersen <teg at jlkm.no>
---
 rc.sysinit |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/rc.sysinit b/rc.sysinit
index 1601e7a..1331587 100755
--- a/rc.sysinit
+++ b/rc.sysinit
@@ -82,7 +82,6 @@ run_hook sysinit_udevlaunched
 # Trigger udev uevents
 if /bin/pidof -o %PPID /sbin/udevd >/dev/null; then
 	stat_busy "Triggering UDev uevents"
-	/sbin/udevadm control --property=STARTUP=1
 	/sbin/udevadm trigger --action=add --type=devices
 	/sbin/udevadm trigger --action=add --type=subsystems
 	stat_done
@@ -101,7 +100,6 @@ unset mods
 if /bin/pidof -o %PPID /sbin/udevd >/dev/null; then
 	stat_busy "Waiting for UDev uevents to be processed"
 	/sbin/udevadm settle --quiet --timeout=${UDEV_TIMEOUT:-30}
-	/sbin/udevadm control --property=STARTUP=
 	stat_done
 fi
 
-- 
1.7.4.2