mdadm >= 3.0 - udev test rule

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

 



Hello,

I have just a simple question about the udev rule:
TEST!="md/array_state", GOTO="md_end" or in the last two releases with
the systemd support: TEST!="md/array_state", ENV{SYSTEMD_READY}="0",
GOTO="md_end".

We are running a XenSever 6.2 system which is based on CentOS 5.7 with
included an old version of udev: udev-095. This version doesn't
support the ATTR keyword so I am going to swap it with the old one
SYSFS, but it appears that udev doesn't recognize as well the TEST
keyword, so I am wondering what exactly this rule is there for? Is it
checking if "md/array_state" appears somewhere in the attributes and
if not it jumps to "md_end"?
And do you have any idea how the rule should be rewritten for older
versions of udev?

Kind regards,
Hristo Chonov,
VKM, TU Darmstadt
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux