On Tue, Oct 25, 2011 at 2:56 PM, clemens fischer <ino-news@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > My system broke with udev-174-1. I have rules renaming eth* according > to their MACs for consistency, guarding against dependency on > order-of-detection, plus rules to customize a wlan running on an USB > device. These rules didn't run. Could you have a look in your logs (dmesg in particular) for any messages? Make sure that logging is turned on in /etc/udev.conf. If a rule does not work, a warning/error should be printed to dmesg. > Basically, there is one rule file[1] calling out to a number of local > "simple" rules. These in turn are very short, containing only (LOCAL_) > "RUN"/"NAME" commands. The main rule assembles a name out of subsystem, > addresses, interfaces etc. This name points into a separate directory > "/etc/udev-local" where the appropriate one- or two liners live, and > there's a logging rule telling me what file names to use if there's > anything missing. All this is less complex than eg. udisks and relies > only on udevd. I can't see what is wrong off-hand, so please file a bug report about this so it is not forgotten. (I didn't figure out how your rules are supposed to work, so there might be something obvious that I missed...). > Are rules in /etc/udev ever called in the new version? Yes, /etc/udev/rules.d/ are called and take precedence over /lib/udev/rules.d/ as always. > Do I need some compatibility to make this happen? Shouldn't be needed. Note that some deprecated things were removed in 174, but you should have been seeing warnings about this for years, so that probably is not the problem here (see the NEWS file for details). Cheers, Tom
