Re: time_t size: The year 2038 bug?

From: Phil Wilshire (philwil@on-ramp.ior.com)
Date: Wed Jan 05 2000 - 18:17:23 EST


James Willard wrote:
>
> > On Wed, 5 Jan 2000 doug@springer.net wrote:
> >
> > > I have tentatively searched the linux kernel archives for this subject,
> > > but haven't found anything. I have heard that there is talk about
> > > moving this to 64 bits. Has anyone considered this (stupid
> > > question) and who else is interested in this subject. It seems to be
> > > a kernel and a glibc issue. Since I am not currently subscribed to
> > > the list, please cc doug@springer.net for any replies. When time
> > > allows, I intend to experiment with the 64 bit thing and see what
> > > breaks.
> > > -Doug Springer
> > >
>
> [snip]
>
> > I think that before 38 years is up, none of us will be using 32-bit
> > machines so, even if I was 10 years old, I wouldn't bother 'fixing'
> > 32-bit machines. Even Intel's new stuff is 64 bits.
>
> Just on a side note, isn't that what they said about two digit dates back in
> the 70's? ;)
>
> James
>

You bet and the time is NOW to fix it.

Memories are still fresh from Y2K

Given the uptime of Linux hopefully some embedded systems
designed this year will still be running then ;-))

regards
  Phil Wilshire

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jan 07 2000 - 21:00:04 EST