On Saturday 30 April 2011 23:00:42 [email protected] wrote: > Hello, > > The time sequence on my "standard" system would be: > > 1. '/lib/udev/rules.d/50-udev-default.rules': > SUBSYSTEM=="rtc", DRIVERS=="rtc_cmos", SYMLINK+="rtc" > > 2. '/etc/udev/rules.d/55-lfs.rules': > # This causes the system clock to be set > # as soon as /dev/rtc becomes available. > SUBSYSTEM=="rtc", ACTION=="add", MODE="0644", \ > RUN+="/etc/rc.d/init.d/setclock start" > > KERNEL=="rtc", ACTION=="add", MODE="0644", \ > RUN+="/etc/rc.d/init.d/setclock start" > > ------ > > I'm reformulating the questions/confusion of my OP: > > 1. FWIW, I don't see the relevance of rule 50-udev above (1)
The rule in 50-udev creates the symlink '/dev/rtc' to the actual node '/dev/rtc0'. It isn't relevant to the clock being set or not being set. > > 2. What is a possible configuration that would trigger > the _SUBSYSTEM_ action in 55-lfs (2) ? *As written*, the subsystem rule is triggered *if* the RTC is in subsystem rtc; if there is no such subsystem, the rule will never be triggered. The kernel rule will never be triggered because it is looking for a device with kernel name 'rtc'; this device doesn't exist. If this rule is changed to look for a device with correct kernel name of 'rtc0', it will be triggered. > 4. I'm still puzzled about not being able to find any traces on the > console about 'setclock' being run by udev (55-lfs above). > Is it possible that "inside" udevd the standard message > "Setting system clock..." goes somewhere else? The log-fog? The log level may be set to, or default to, 'err'. If you change it via udevadm control --log-priority=info or udevadm control --log-priority=debug you should see all the info you're looking for--'debug' will show a *ton* of info. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
