Kay Sievers f7c5b04f69 re-enable failed event tracking ... It did not work for the last couple of releases. If RUN{record_failed}+="..." is given, a non-zero execution will mark the event as failed. Recorded failed events can be re-triggered with: udevadm trigger --type=failed The failed tracking _might_ be useful for things which might not be ready to be executed at early bootup, but a bit later when the needed dependencies are available. In many cases though, it indicates that something is used in a way it should not.		2009-08-06 16:16:26 +02:00
..
50-udev-default.rules	rules: set group ownership of new firewire driver device files	2009-07-01 23:43:17 +02:00
60-persistent-alsa.rules	rules: sound - move from udev-extra	2009-06-16 20:26:20 +02:00
60-persistent-input.rules	rules: exclude digitizers from joystick class	2009-08-05 05:07:15 +02:00
60-persistent-serial.rules	rules: serial - fix path_id call	2009-07-23 20:30:52 +02:00
60-persistent-storage-tape.rules	path_id: implement in C using libudev	2009-06-06 16:07:06 +02:00
60-persistent-storage.rules	rules: make ata_id properties the default for all ATA block devices	2009-06-28 02:59:48 +02:00
75-net-description.rules	rules: tty/net - move from udev-extras	2009-06-16 20:27:22 +02:00
75-tty-description.rules	rules: tty/net - move from udev-extras	2009-06-16 20:27:22 +02:00
78-sound-card.rules	rules: sound - move from udev-extra	2009-06-16 20:26:20 +02:00
80-drivers.rules	re-enable failed event tracking	2009-08-06 16:16:26 +02:00
95-udev-late.rules	send monitor events back to netlink socket	2009-03-29 04:24:39 +02:00