>No!
>Even my ancient Cyrix 686 166+ happily clicked over to 1/1/2000. The only
>problem I have heard of is a company in the US whose system crashed when
>they tested it a couple of days before the new year. Maybe everyone took
>sufficient measures ahead of time.
A Cyrix is hardly ancient. And it's not the processor that matters but
the RTC. Linux, like Unices, doesn't have a Y2K problem in the kernel,
but a Y2038 problem, which will be fixed as time_t is becoming a 64
bit integer (it already is in glibc). So leaving your computer on is
no test. Turning it on again after NY is, because the system time gets
loaded from the RTC. I think the Linux hardware clock utilities know
how to deal with RTCs that wrap around to 1980.
I'd like now to see those doom and gloom Y2K bug alarmists go crawl
under a rock in shame. :-)
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
