On Thu, May 27, 2010 at 01:03, Paul Stewart <pstew@xxxxxxxxxx> wrote: > Fix udev issue where temporary persistent rules are written in one > place and read from another. The upstream udev release placed dynamic > persistent rules (ones that get deleted every reboot) in /dev/.udev/, > but the actual udev daemon read these rules out of > /dev/.udev/rules.d/. I think these temporary rules have never been expected to be read by the udev daemon directly. > The side effect of this is that if the static > directory (/etc/udev/rules.d) is not writeable (read-only root > filesystem, for example), device interfaces keep getting renamed > wlan0, wlan1, wlan2, etc, if they are plugged and unplugged or if > udevd restarts. The temporary rules files, which might be created in /dev/.udev/ are supposed to be copied to /etc/udev/rules.d/ as soon as the rootfs is writable. There should be no restart of udevd in the meantime. :) What kind of system you are seeing problems? Is it a known distribution? How do you handle the temporary rules files you copy into /dev/.udev/rules.d/? How do they get into /etc? > Note that this change by itself won't work on most distributions (with > read only fses) unless they they also make sure that the > /dev/.udev/rules.d directory is created before udevd starts up, since > otherwise the inotify will never trigger for that directory since it > didn't exist when the inotify call was made. What do you mean? Udevd itself creates this directory, and watches it with inotify. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
