summaryrefslogtreecommitdiff
path: root/rules/rules.d/80-drivers.rules
AgeCommit message (Collapse)Author
2012-03-07rules: move all rules to top level rules/ dirKay Sievers
2011-12-23rules: do not preprocess 80-drivers.rules + 75-probe_mtd.rulesKay Sievers
2011-12-05use libexecdir, bindir, sbindir, switch to /usr/lib/udev in documentationKay Sievers
2011-10-19rules: do not load sg moduleKay Sievers
2010-05-27rules: add -v to modprobe calls to be able see what will be loadedKay Sievers
2010-04-13rules: call modprobe on all events but "remove"Kay Sievers
2009-08-06re-enable failed event trackingKay Sievers
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-06-17rules: remove MMC rule, 2.6.30 has the modaliasKay Sievers
2009-06-10rules: remove scsi ch module loading ruleKay Sievers
2008-12-19rules: first simple step merging with Ubuntu rulesKay Sievers
2008-12-19rules: remove ide-scsiKay Sievers
2008-11-13rules: remove pnp shell script, acpi loads these modules properlyKay Sievers
2008-07-18move default rules from /etc/udev/rules.d/ to /lib/udev/rules.d/Kay Sievers
None of these rules is supposed to be changed by users, so move them out of /etc. Custom rules, and automatically generated rules stay in /etc. All rules are still processed in lexical order, regardless which directory they live in.