Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucla-cs.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!trwrb!trwrba!cepu!ucla-cs!das
From: das@ucla-cs.UUCP
Newsgroups: net.bugs,net.flame,net.puzzle
Subject: Re: Computer bugs in the year 2000
Message-ID: <3363@ucla-cs.ARPA>
Date: Wed, 23-Jan-85 19:41:43 EST
Article-I.D.: ucla-cs.3363
Posted: Wed Jan 23 19:41:43 1985
Date-Received: Sun, 27-Jan-85 05:38:40 EST
References: <820@reed.UUCP> <20381@arizona.UUCP>
Reply-To: das@ucla-cs.UUCP (David Smallberg)
Organization: UCLA Computer Science Department
Lines: 8
Xref: watmath net.bugs:516 net.flame:8051 net.puzzle:520
Summary: 

From what I've read, many programs broke at the start of 1970 because they
stored the year as a single digit; fewer, but still a good number, broke in
1980.  I think the real trouble will come on January 3, 2000, not January 1,
since the 3rd is the first business day.  I think the problems will come
in subtle ways -- most companies will catch the obvious implications of a
two-digit year cycling around, but buried away in some obscure code...

-- David Smallberg, das@ucla-cs.ARPA, {ihnp4,ucbvax}!ucla-cs!das