On Thu, Nov 03, 2005 at 08:28:12AM -0700, Archaic wrote: > On Thu, Nov 03, 2005 at 09:47:54AM -0100, Duncan Webb wrote: > > > > > Maybe I was not too clear. > > No, you were perfectly clear. > > > If the system clock is set to local time then when you shut-down the > > hardware clock should be set to system time. > > And again, no. LFS cannot assume the sanity of the system clock so it > should not write to the hwclock. NTP gives us the sanity, therefore, NTP > is where the symlinks are made.
This is all true in general, however, I'm starting to think that DST considerations might override that at 2 points during the year. If the user is running NTP, then there's no problem (and as you say, the symlinks are created when NTP is installed). If the user puts their RTC in UTC time, then there's also no problem. (So Duncan, this is your fix: Put your hardware RTC in the UTC timezone, then it won't have to change when DST starts or stops. If you dual boot to less intelligent OSes, then that's a poor fix, but it would at least prevent this problem. Or, set up NTP.) But if the RTC is in localtime, and localtime changes its offset from UTC, then perhaps the RTC should be offset at that time. It is true that we don't know whether the system clock or the hardware clock is more accurate in general, but if we're talking about an hour difference at DST switchover, the accuracy difference between the system and hardware clocks is likely miniscule in comparison. Note that I have no idea *how* the bootscripts could handle that, just that I think it may be appropriate to set the RTC in this one case. If it's impossible, then that's fine.
pgpSLvRM0aPV5.pgp
Description: PGP signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
