From owner-freebsd-stable@FreeBSD.ORG Tue Oct 30 07:23:30 2007 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFC5E16A41B; Tue, 30 Oct 2007 07:23:30 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 5513013C4B2; Tue, 30 Oct 2007 07:23:28 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id l9U6Yxfh095765; Tue, 30 Oct 2007 13:34:59 +0700 (KRAT) (envelope-from eugen@kuzbass.ru) Message-ID: <4726D08D.C4BC054A@kuzbass.ru> Date: Tue, 30 Oct 2007 13:34:53 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: Doug Barton References: <20071028083955.GA69713@svzserv.kemerovo.su> <20071028171921.GB18965@svzserv.kemerovo.su> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org Subject: Re: CMOS, daylight saving time and dual-boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 07:23:30 -0000 Doug Barton wrote: > > Suppose, the machine does not have global connectivity at all > > (and it has no local source of exact time) or just at the boot time. > > It still needs to adjust local time, right? > > Your post posited a problem with ntpd not being able to synch the time > because it was an hour off. The fact that the DST problem caused the ntp > problem isn't really relevant. > > > It seems to me as DST problem really, not NTP problem. > > I don't think I properly stated my actual point, which is that the issue > you're describing is an edge case, and we have about 1k more important > things that need developer time. > > If you choose to spend some of your time fixing this problem I'm sure we'd > all be interested in your results. I did some investigations about the issue. It seems there are two things to be done to fix this: 1) Choose a place to keep DST flag that was actual at the moment of last shutdown. It may be CMOS bit or on-disk file. On-disk file is less suitable for diskless stations but they can't run Windows anyway and should keep its CMOS times in UTC. OTOH, CMOS flag may be shared between several OS'es. 2) Teach 'adjkerntz -i' to respect the flag whenever it resides and adjust machdep.adjkerntz as needed. Both tasks are pretty simple and require just an accurate implementation. I'll try to find time for this. Eugene Grosbein