Date: Mon, 3 Apr 2000 11:25:44 -0400 From: Peter Radcliffe <pir@pir.net> To: freebsd-stable@freebsd.org Subject: Re: dufus.[...] daily run output -- summer time Message-ID: <20000403112544.A6526@pir.net> In-Reply-To: <200004031510.LAB21697@radagast.wizard.net>; from tyson@stanfordalumni.org on Mon, Apr 03, 2000 at 11:09:52AM -0400 References: <14568.45040.795743.139682@kci.kciLink.com> <200004031510.LAB21697@radagast.wizard.net>
next in thread | previous in thread | raw e-mail | index | archive | help
"Donald R. Tyson" <tyson@stanfordalumni.org> probably said: > 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. This is normal. 'doze keeps the PC's system time as local time, so all it does when it works out it's booted the first time after a timechange (and probably if it is up over a timechange) is add/subtract an hour from the current time. If you run a FreeBSD box with local time in the system clock (which of course you have to to make doze have the correct time), it does the same thing. Boot both after a timechange, you get 2 hours difference, 1 from each. On my dualboot boxes I turn off automatic time changes in doze. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000403112544.A6526>