Michael
No favorite files added yet
(Mar 1, 2007 - 6:32 PM)
While some posters have touched upon the various issues, I didn't see anyone who included all of them in one go.
Basically, it's not as easy as setting the clock at the right time, whether it be manually or through NTP. If you're synchronized with an NTP server, your machine on March 11th will do what it has always done: adjust its notion of GMT time.
But that's not all. The computer also has a notion of local time. So this needs to be taken into account, too.
Lastly, there *ARE* some applications that maintain their own notions of localtime. For example, all Java JREs will need to be either patched or replaced, because they maintain their own timezone tables independently of the operating system.
So, it's not an entirely trivial affair. One good thing that might happen is that administrators and end users might be urged/inspired to migrate away from MS products that are in their extended support phase. More specifically, I think it's a generally good idea for people to move to more recent products, as those products are most often more stable and usable and secure (at least we hope).