From owner-freebsd-stable@FreeBSD.ORG Sun Oct 28 11:08:32 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 D8C6E16A418 for ; Sun, 28 Oct 2007 11:08:32 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id D601013C48D for ; Sun, 28 Oct 2007 11:08:28 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id l9SB8QnU083602; Sun, 28 Oct 2007 18:08:26 +0700 (KRAT) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id l9SB8QR9083601; Sun, 28 Oct 2007 18:08:26 +0700 (KRAT) (envelope-from eugen) Date: Sun, 28 Oct 2007 18:08:26 +0700 From: Eugene Grosbein To: Peter Jeremy Message-ID: <20071028110826.GA83337@svzserv.kemerovo.su> References: <20071028083955.GA69713@svzserv.kemerovo.su> <20071028103508.GQ70883@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071028103508.GQ70883@server.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.3i 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: Sun, 28 Oct 2007 11:08:32 -0000 On Sun, Oct 28, 2007 at 09:35:08PM +1100, Peter Jeremy wrote: > Based on a quick check, it doesn't look like adjkerntz(8) can handle > your situation. In the absence of any independent time source, it's > actually very difficult to handle this situation. In theory, it would > be possible to note that the last system shutdown (or last time the > RTC was set) and determine whether there's been a DST transition in > the period between then and now and adjust the RTC appropriately (I > believe Windows does this). The problem is that, unless this record > is kept within the RTC and all OSs co-operate in its meaning, each > OS will independently adjust the RTC when it is next rebooted (and > I believe multi-boot PCs run into this problem). It would be possible to utilize a bit in the CMOS at boot time to decide if BIOS time set to Summer time and clear it appropriately, in theory :-) Eugene