On Sep 25, Petter Reinholdtsen <p...@hungry.com> wrote: > I was told that udev would run the udev rule to set the system clock > if it was enabled, and thus believed it would be sufficient to look > for the existence of /dev/.udev to decode when to disable the init.d > scripts. Obviously this assumtion is not quite right. I have asked There is no doubt that a RUN rule matching on KERNEL=="rtc0" is triggered even if the driver is built-in.
Let's try some simple and stupid debugging. Somebody who can reliably reproduce the problem please add something like this to the *end* of /lib/udev/rules.d/85-hwclock.rules : KERNEL=="rtc0", RUN+="/bin/touch /dev/rtc0-appeared" KERNEL=="rtc0", RUN+="logger.agent" > Anyway, a workaround if the udev rule only work when rtc is a kernel > module, would be a patch like this, to only disable the init.d scripts This would only cure the symptoms. Please Cc me on updates. -- ciao, Marco
signature.asc
Description: Digital signature
