On Thu, May 27, 2010 at 15:55, Paul Stewart <pstew@xxxxxxxxxx> wrote: > So I was confused about who if anyone puts rules in /dev/.udevd/ > rules.d. I read the comment in the generator code and it seemed to > imply that the location it was writing to would be seen by udev, so I > just assumed it was a mistake and merged the two. If that's not > correct, could someone clarify why that is worse than what is there > now? This way rules created by the generator go directly into udev > instead of waiing until later in the boot cycle. I guess the generator is older than the /dev/.udev/rules.d/ directory. We could think about moving these rules there. Not sure, if there are any unwanted side-effects. > Secondly, assuming the current configuration has always been the case, > I would assume nobody has actually tested that inotify works on / > dev/.udevd/rules.d if the directory does not already exist before > udevd has started. I have done this myself and it does not. If that is > unexpected behavior for udevd, I'll hunt down the issue in the C code > and send a patch for that instead of one for the unit script. The generator run from udev rules, started by udevd. How should anything write a rule when udevd is not running? :) 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
