I'm trying to write a set of udev rules for managing rotated backup
drives. The real system this is going on is Red Hat 5.3. The scratch
machine I've been working on is Ubuntu 10.04. (There's a ton of
documentation out there that's old that doesn't really work with
either machine.)
Since I'm actually trying to manage two drives which could possibly be
mounted at the same time, I'm using a script rather than trying to do
everything in the rule. So far, at least on ubuntu, this works:
ACTION=="add", KERNEL=="sd[a-z][0-9]", SUBSYSTEM=="block",
RUN+="/usr/local/bin/usb_block_added %k"
ACTION=="remove", KERNEL=="sd[a-z][0-9]", SUBSYSTEM=="block",
RUN+="/usr/local/bin/usb_block_removed %k"
But:
ACTION=="add", KERNEL=="sd[a-z][0-9]", SUBSYSTEM=="block",
ENV{ID_FS_LABEL}=="backup", RUN+="/usr/local/bin/usb_block_added %k"
does not. udevadm test /block/sdd3 appears to show the rules file is
being processed as expected. If I remove ENV{ID_FS_LABEL} and test for
that environment variable in the script, it is present and contains
the expected value.There are log messages in /var/log/daemon about
SYSFS{} will be removed, but they come from Ubuntu rules
(45-hpdjconsole), not this rule.
Can I use ID_FS_LABEL in my rules or must it be relegated to the script?
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
