From owner-freebsd-hackers Mon Nov 26 23:10:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AAA5937B41B for ; Mon, 26 Nov 2001 23:10:41 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id fAR7Aea03721; Tue, 27 Nov 2001 00:10:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id fAR7AcM10976; Tue, 27 Nov 2001 00:10:39 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200111270710.fAR7AcM10976@harmony.village.org> To: Zwane Mwaikambo Subject: Re: [PATCH] Relevance of 8254 calibration. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 27 Nov 2001 09:11:38 +0200." References: Date: Tue, 27 Nov 2001 00:10:38 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Zwane Mwaikambo writes: : When you say system time do you mean "hardware" time? or the running : kernel's time? Output of date command, which is kept by the kernel. : The hardware time doesn't work anyway since the box's RTC : is stuck somewhere in 2057 but the hardware timer interrupt seems to be : ticking at the right pace so i'm sure the kernel time does stay consistent : (with normal drift). I had problems regarding timestamps on files in Linux : (annoying because configure scripts would think the files have changed : whilst it was running and hence an endless loop) but i don't seem to have : the same problem in FreeBSD. Cool. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message