Hi all
I tried this out on my PC ...
Things worked fine ..well almost
Only error messages were related to system clock which was set to yr
1901. Rest Every thing worked fine including X-server.
I logged in(KDE) and everythig was okay. But when i logged in Gnome
..X-server crashed.
Why this difference in behavior .. difference in distros?? (i use FC2)

and is windows free of this bug ??

Harpreet
On Mon, 2005-05-09 at 16:48, Tarun Kant wrote:
> Hi All,
>
> To test how bad this so called Y2038 bug is, I thought to do an experiment
myself. Saturday when I left, I changed my system date to 18th January 2038. On
Sunday, in the morning when I booted the computer, first thing that went wrong
was that X server failed to start on it's own neither did ethernet. All that I
got was the Linux command line screen. I logged in as normal user and it showed
me system date as 14th December 1901 (instead of 19th Jan 2038) and 3:21 am as
the current time (instead of normal time which should have remained the same at
10:51 am). I decided to started the X server and it did start flawlessly, but as
soon as KDE was up and running the audio server crashed. Firefox would not start
clean (...no wonders, the certificates at that date did not exist). Playing
around a little bit I could see the system was all messed up. By the way, I am
running the latest 'Mandriva Limited Edition 2005' currently, which is by far my
favourite one (many of you will remember my Mandrake loyalty, I keep falling
back to it time after time; will tell you about Mandriva experience later
though).
>
> So after this time-travel experiment of sorts where I had seen
this-some-what-devastating effect of this bug on my system, I decided to revert
back to the normal date and time. And after the date and time change to normal
and a reboot, every thing seems to be working except my ethernet, which is still
dead. I have looked into all the settings, just every possible thing, but it
does not start now. I don't understand what could have possibly gone wrong. If
anyone can throw some light on what might have happened. I fail to understand
that how this date problem has disabled my eth0? Any suggestions?
>
> I however feel that though this is a serious issue, but year 2038 is still
more than 32 years away and that is enough time to sort this problem out. Except
for the embedded linux based system which probably will be harder to fix. But
then 32 years is a long time. Though I reckon that this is much more serious a
problem than the much hyped Y2K bug.
>
> -Tarun
>
>