1. OT: oh man!
remember that little C proggy i whipped up that converts UNIX time?
well, UNIX time is a signed number counting in seconds since january 1,
1970. the problem is, since it's signed it lasts half as long! so i did
a little test with my prog on my linux box, and 2147483648(the second
immediately after January 19, 2038, 3:14:07 AM) was interpreted as
January something 1901!!! why hasn't anybody fixed the kernel yet? i
would, but on a dialup connection it'd take a long time, i have no clue
how to compile the kernel and put it to use, and i'd have to wade
through countless lines of code to find the one line...
2. Re: OT: oh man!
Fixing the kernel is the easy part.
The hard part is changing all of the HUNDREDS/THOUSANDS of proggy's
that depend on the time being signed.
Regards
Brian Keene
--- sephiroth _ <euman2376 at yahoo.com> wrote:
>
> remember that little C proggy i whipped up that converts UNIX time?
> well, UNIX time is a signed number counting in seconds since january
> 1,
> 1970. the problem is, since it's signed it lasts half as long! so i
> did
> a little test with my prog on my linux box, and 2147483648(the second
>
> immediately after January 19, 2038, 3:14:07 AM) was interpreted as
> January something 1901!!! why hasn't anybody fixed the kernel yet? i
> would, but on a dialup connection it'd take a long time, i have no
> clue
> how to compile the kernel and put it to use, and i'd have to wade
> through countless lines of code to find the one line...
>
>
>
