From owner-freebsd-hackers  Sun Feb 13  0:57:14 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by builder.freebsd.org (Postfix) with ESMTP id 284AB4053
	for <hackers@FreeBSD.ORG>; Sun, 13 Feb 2000 00:57:10 -0800 (PST)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA58797;
	Sun, 13 Feb 2000 01:57:14 -0700 (MST)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA62668; Sun, 13 Feb 2000 01:58:45 -0700 (MST)
Message-Id: <200002130858.BAA62668@harmony.village.org>
To: Brian Beattie <beattie@aracnet.com>
Subject: Re: CMOS clock won't do 2000 
Cc: hackers@FreeBSD.ORG
In-reply-to: Your message of "Sat, 12 Feb 2000 12:57:46 PST."
		<Pine.LNX.4.10.10002121248470.12446-100000@shell1.aracnet.com> 
References: <Pine.LNX.4.10.10002121248470.12446-100000@shell1.aracnet.com>  
Date: Sun, 13 Feb 2000 01:58:45 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <Pine.LNX.4.10.10002121248470.12446-100000@shell1.aracnet.com> Brian Beattie writes:
: I have an older 486 system, running 3.4R that has a cmos clock that seems
: to be unwilling to accept years out side the range 94-99.  The bios seems
: willing to set dates between 1994-2099, but after reboot any year not
: between 94-99 is converted to {20,19}94.

ntpdate on boot is what we use in the village for this sort of thing.
We run ntp at other times.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message