zfs/scripts
Brian Behlendorf e0aff96a14 Use udevadm if available otherwise use udevtrigger/udevsettle
Moving forward udevadm {trigger/settle} replaced udevtrigger/udevsettle
as the correct interface to use.  However, since we need to work in
both environments for testing check and see if udevadm is available.
If it is then use it.  If it is not fall back to the legacy interface.
2010-01-08 10:20:03 -08:00
..
udev-rules Add 16 drive promise JBOD zpool configs for small test setup. 2009-11-20 10:12:41 -08:00
zpool-config Add 16 drive promise JBOD zpool configs for small test setup. 2009-11-20 10:12:41 -08:00
Makefile.am Add udev rules to zfs-test package 2009-11-24 15:48:16 -08:00
common.sh Use udevadm if available otherwise use udevtrigger/udevsettle 2010-01-08 10:20:03 -08:00
zconfig.sh Additional ZVOL compatibility autoconf checks and zconfig ZVOL sanity test. 2009-11-20 10:04:56 -08:00
zfs-update.sh Merge commit 'refs/top-bases/zfs-branch' into zfs-branch 2009-12-11 16:22:24 -08:00
zfs.sh Add zfs-test package which includes test infrastructure. 2009-08-17 21:35:06 -07:00
zpool-create.sh Update zpool-configs to be udev aware. 2009-10-21 11:38:51 -07:00