From owner-freebsd-questions Fri Jan 16 14:13:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00780 for questions-outgoing; Fri, 16 Jan 1998 14:13:43 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00744 for ; Fri, 16 Jan 1998 14:13:27 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id IAA03880; Sat, 17 Jan 1998 08:21:04 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id IAA22253; Sat, 17 Jan 1998 08:21:03 +1030 (CST) (envelope-from grog) Message-ID: <19980117082103.15484@lemis.com> Date: Sat, 17 Jan 1998 08:21:03 +1030 From: Greg Lehey To: Greg King Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Y2K & 2.2.1 References: <34BFA56D.C3241230@c-com.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <34BFA56D.C3241230@c-com.net>; from Greg King on Fri, Jan 16, 1998 at 12:22:37PM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Fri, Jan 16, 1998 at 12:22:37PM -0600, Greg King wrote: > I looked for info on the year 2000 bug and haven't found any via the > search engine in your > support area. > > The reason I ask is I think I found one in the DATE command for 2.2.1. > > The reason I say this is that it uses the YYMMDD format which means it > will roll over to > > 000101 at the year 2k. Correct. What's the problem? The year value represents the last two digits of a year between 1970 and 2038. Why not try it? # date 6811130711 date: nonexistent time # date 7011130711 Fri Nov 13 07:11:00 CST 1970 # date 9911130711 Sat Nov 13 08:11:00 CST 1999 # date 0011130711 Mon Nov 13 07:11:00 CST 2000 # date 3711130711 Fri Nov 13 07:11:00 CST 2037 # date 3811130711 date: nonexistent time # date 3801130711 Wed Jan 13 07:11:00 CST 2038 # The reason January 2038 works, and November 2038 doesn't, is because the time stamp wraps some time in 2038. By then I'm sure we'll have thought of a fix. Greg