+grml-udev-config (0.0.4) unstable; urgency=low
+
+ * grml-blockdevices rule: do not react on changes in block devices
+ but instead on any add|change|remove action on filesystem layer.
+ Move script from priority 60 to 90 to be able to access
+ ID_FS_USAGE. Thanks for help to Ulrich.
+
+ -- Michael Prokop <mika@grml.org> Sat, 03 Apr 2010 02:49:38 +0200
+
grml-udev-config (0.0.3) unstable; urgency=low
[ Ulrich Dangel ]
# regenerate /etc/fstab for new/removed devices:
-ACTION=="add", SUBSYSTEM=="block", RUN+="/usr/sbin/rebuildfstab -r -config"
-ACTION=="remove", SUBSYSTEM=="block", RUN+="/usr/sbin/rebuildfstab -r -config"
+ENV{ID_FS_USAGE}=="filesystem", ACTION=="add|change|remove", SUBSYSTEM=="block", RUN+="/usr/sbin/rebuildfstab -r -config"
+#ACTION=="add", SUBSYSTEM=="block", RUN+="/usr/sbin/rebuildfstab -r -config"
+#ACTION=="remove", SUBSYSTEM=="block", RUN+="/usr/sbin/rebuildfstab -r -config"
dh_installudev --name=grml-forensic --priority 01
dh_installudev --name=grml-external --priority 60
dh_installudev --name=grml-usbdev --priority 60
- dh_installudev --name=grml-blockdevices --priority 60
+ dh_installudev --name=grml-blockdevices --priority 90
dh_installinit --no-start --name=grml-udev
# do *NOT* automatically install it, see README.Debian
# --update-rcd-params='start 03 S .'