From owner-freebsd-stable Mon Apr 3 17:40:25 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.rdc3.on.home.com (mail1.rdc3.on.home.com [24.2.9.40]) by hub.freebsd.org (Postfix) with ESMTP id 8920437B74A for ; Mon, 3 Apr 2000 17:40:07 -0700 (PDT) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail1.rdc3.on.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <20000404004006.ONSB22000.mail1.rdc3.on.home.com@tristan.net>; Mon, 3 Apr 2000 17:40:06 -0700 Content-Length: 753 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200004031510.LAB21697@radagast.wizard.net> Date: Mon, 03 Apr 2000 20:34:37 -0400 (EDT) From: Colin To: "Donald R. Tyson" Subject: Re: dufus.[...] daily run output -- summer time Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Had you booted the Win side first, then the FreeBSD side, you would have seen FreeBSD trying to move the clock ahead "2" hours. It knows it hasn't moved the time ahead yet so it adds 1 hour to the current BIOS time, which had already been moved ahead by the previous OS boot. You'll see this behaviour on any dual boot system. On 03-Apr-00 Donald R. Tyson wrote: > [cc: deleted] > > As a moderately humorous aside, when I booted the Windows > side of my home machine on Sunday afternoon, it proudly > informed me that it had adjusted for the time change, and > then displayed a **2-hour** leap ahead. > > At least the 4.0-STABLE side, despite the error reported by > several on this list, managed to get the time right. > cheers, Colin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message