1997-07-30 - Re: y2k problem serious

Header Data

From: ghio@temp0104.myriad.ml.org (Matthew Ghio)
To: cypherpunks@cyberpass.net
Message Hash: 0090d9eaebe421b95b0eceeb9cfb3e44ca1444bd3f12c77b7b8e3080d608fcb8
Message ID: <199707292351.QAA24907@myriad.alias.net>
Reply To: <199707290054.RAA21755@netcom13.netcom.com>
UTC Datetime: 1997-07-30 00:03:00 UTC
Raw Date: Wed, 30 Jul 1997 08:03:00 +0800

Raw message

From: ghio@temp0104.myriad.ml.org (Matthew Ghio)
Date: Wed, 30 Jul 1997 08:03:00 +0800
To: cypherpunks@cyberpass.net
Subject: Re: y2k problem *serious*
In-Reply-To: <199707290054.RAA21755@netcom13.netcom.com>
Message-ID: <199707292351.QAA24907@myriad.alias.net>
MIME-Version: 1.0
Content-Type: text/plain

Ray Arachelian wrote:
> And don't forget about the year 2038 problem

This is probably more serious than the year 2000 problem.  Unix/posix has
become the de facto standard operating system.  Apple has already migrated
to a unix/mach kernel.  Even Microsoft's NT has substantial amounts of
unix-derived code.  You're kidding yourself if you think this software
won't be around in some form fourty years from now.

The fix is (seemingly) simple:
  typedef unsigned long int time_t;

Which will give you a year 2106 problem instead. :)

That'll at least fix most email systems.  InterNetNews will need a bit
more work to prevent it from trashing its history file come 3:14am
on January 19, 2038.

"Death of usenet predicted; film at 11..."