From owner-freebsd-chat Thu Nov 20 06:54:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA09307 for chat-outgoing; Thu, 20 Nov 1997 06:54:18 -0800 (PST) (envelope-from owner-freebsd-chat) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id GAA09302 for ; Thu, 20 Nov 1997 06:54:14 -0800 (PST) (envelope-from jamie@itribe.net) Message-Id: <199711201453.JAA00792@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Thu, 20 Nov 1997 09:52:39 -0500 (EST) From: Jamie Bowden To: James Raynard cc: freebsd-chat@freebsd.org Subject: Re: Tell the world about Year 2000 Compliance In-Reply-To: <19971120001625.00506@jraynard.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 20 Nov 1997, James Raynard wrote: > Although the problem isn't just a case of handling 1st January 2000 > correctly - there may be programs which (wrongly!) assume 2000 is not > a leap year. I vaguely remember hearing about some system which got > past 1st Jan and 29th Feb 2000, only to miss out a day in the middle > of March (OK, I think that one was a hardware bug). Why is it wrong to assume 2000 isn't a leap year? Last time I checked, years ending in three 0's were not leap years by definition. Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle)