Ec|ipse wrote:
>
> Scott Watson wrote:
> >
> > From: Harald Sundt <[EMAIL PROTECTED]>
> > >How does Y2K affect the Linux Platform or Apps?
> >
> > I understand that, while Linux is 2000 OK, it may have problems in 2038.
> > Can anyone expand on this?
> >
>
> In a nut shell, thats when the internal clock on the system will have
> reached its 32bit (was it 32?) limit. Theres already talk about changing
> it to a 64 bit number, but I'm not sure when that would be implemented.
I'll bet before 2036 ;->
Seriously, Linux is already going 64 bit, and the time in
the
64 bit code is also 64 bit, so this will be a non-issue for
64 bit Linux (or so says Linux Journal a couple months
back).
I figure 64 bit Linux will be commonplace by 2005, so there
really isn't anything to worry about. This really isn't
unrealistic - look at all the 8008's and 8080 processors
running
around - not very many!!! Anyone running i386-based PC's
30 years from now deserves what they get.
Finally, Microsoft based their Office product's time
measurement
on the same algorithm that Unix (and Linux) uses, so they,
too,
have the dreaded 2036 bug.
This is all based on 2^32 seconds from 1900, which is
2036.195,
or March 10th, 2036 (plus or minus a couple days). I'll be
in
my rocking chair with my 128-bit 25 gigaflops antique by
then.
George
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
