#2497: setclock boot script does not start in stable LFS 6.5
-------------------------+--------------------------------------------------
 Reporter:  ruslan.st    |       Owner:  lfs-b...@…                   
     Type:  defect       |      Status:  new                          
 Priority:  normal       |   Milestone:  6.6                          
Component:  Bootscripts  |     Version:  6.5                          
 Severity:  normal       |    Keywords:  bootscripts setclock         
-------------------------+--------------------------------------------------
Changes (by br...@…):

  * milestone:  => 6.6


Comment:

 That's because it runs from a udev rule now; see 55-lfs.rules:

 {{{
 # This causes the system clock to be set as soon as /dev/rtc becomes
 available.
 SUBSYSTEM=="rtc", MODE="0644", ACTION=="add",
 RUN+="/etc/rc.d/init.d/setclock start"
 }}}

 Leaving this open, however, as there has been some discussion lately that
 seems to point to a need to duplicate that rule for KERNEL=="rtc" (old
 non-rtc-class kernels) as well as SUBSYSTEM=="rtc".  (We should probably
 also reorder the keys, to put the MODE assignment after the ACTION match.)

 If hwclock is getting run, this isn't a bug.  If it doesn't run, then I
 would suspect you can get it to run by changing SUBSYSTEM to KERNEL in
 that rule (or by adding a duplicate).

 As far as kill links go: We removed those a couple releases ago.  See the
 BLFS book's section on ntpd if you want them.  (We figure in the absence
 of an external time source, there's no particular reason to believe that
 the system clock is any more accurate than the hardware clock.  Non-timer
 hardware interrupts, along with the fact that the kernel is not real-time,
 make it jitter, or drift completely.)

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2497#comment:1>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to