From owner-freebsd-stable@FreeBSD.ORG Tue Oct 30 06:53:31 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 BC9BC16A419 for ; Tue, 30 Oct 2007 06:53:31 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 5747713C4AC for ; Tue, 30 Oct 2007 06:53:31 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 28250 invoked by uid 399); 30 Oct 2007 05:53:23 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 30 Oct 2007 05:53:23 -0000 X-Originating-IP: 127.0.0.1 Date: Mon, 29 Oct 2007 22:53:21 -0700 (PDT) From: Doug Barton To: Eugene Grosbein In-Reply-To: <20071028171921.GB18965@svzserv.kemerovo.su> Message-ID: References: <20071028083955.GA69713@svzserv.kemerovo.su> <20071028171921.GB18965@svzserv.kemerovo.su> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 06:53:31 -0000 On Mon, 29 Oct 2007, Eugene Grosbein 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. Doug -- This .signature sanitized for your protection