From owner-freebsd-hubs Sat Mar 4 13:16:49 2000 Delivered-To: freebsd-hubs@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id C99FF37B886 for ; Sat, 4 Mar 2000 13:16:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA22291; Sat, 4 Mar 2000 13:16:46 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA83827; Sat, 4 Mar 2000 13:16:46 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 4 Mar 2000 13:16:46 -0800 (PST) Message-Id: <200003042116.NAA83827@vashon.polstra.com> To: mariusz@kam.pl Subject: Re: cvsupd & old date In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: hubs@freebsd.org Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , mariusz wrote: > > I changed involuntarily date in my system on 1944 I assume this was some kind of Y2K work around. > This only such little attention :>> > > from cvsup.log > > CVSup update begins at 1944/05/04 08:20:02 > Updating from cvsup.internat.freebsd.org > > > *** > *** runtime error: > *** Value out of range > *** file "../src/uid/Common/TimeStamp.m3", line 63 > *** Naturally! The code aborts because it thinks it hasn't been written yet. :-) Seriously, I'm sorry you're experiencing this problem. But if you want this fixed I think you'll probably have to fix it yourself. I just can't get very excited about trying to support systems which think it is 1944. Sorry. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message