[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[virt-tools-list] [osinfo PATCH] Use ENV{} in udev rule



There are only a handful of key names that can be directly assigned
in an udev rule (through FOO=....), for device-specific properties,
ENV{FOO} must be used.
---
 data/95-osinfo.rules.in |   16 ++++++++--------
 1 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/data/95-osinfo.rules.in b/data/95-osinfo.rules.in
index 86ff740..33e5986 100644
--- a/data/95-osinfo.rules.in
+++ b/data/95-osinfo.rules.in
@@ -26,16 +26,16 @@ ACTION=="change", \
 ACTION=="change", \
  SUBSYSTEM=="block", \
  ENV{ID_FS_TYPE}!="iso9660", \
- OSINFO_BOOTABLE="", \
- OSINFO_INSTALLER="", \
- OSINFO_LIVE="", \
- OSINFO_MEDIA=""
+ ENV{OSINFO_BOOTABLE}="", \
+ ENV{OSINFO_INSTALLER}="", \
+ ENV{OSINFO_LIVE}="", \
+ ENV{OSINFO_MEDIA}=""
 
 ACTION=="change", \
  SUBSYSTEM=="block", \
  ENV{ID_FS_TYPE}!="udf", \
- OSINFO_BOOTABLE="", \
- OSINFO_INSTALLER="", \
- OSINFO_LIVE="", \
- OSINFO_MEDIA=""
+ ENV{OSINFO_BOOTABLE}="", \
+ ENV{OSINFO_INSTALLER}="", \
+ ENV{OSINFO_LIVE}="", \
+ ENV{OSINFO_MEDIA}=""
 
-- 
1.7.7.6


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]