I awoke this morning with the intention of going through and resetting the clocks on all my computers manually to avoid the hassle of patching them. My two Windows boxen (desktop and laptop) still were in Standard Time, so I advanced them an hour, planning to undo the automatic change when DST would have been going to have arrived in three weeks.
Then I logged into my two Linux boxen, only to find that they had taken care of it themselves. Holy carp, how did that happen?
Then it hit me. The change to the DST boundaries happened in 2005. Surely I’ve updated something on them in the past year and a half or so, yes? Beats me as to when, but apt under Debian updates everything but the kitchen sink if you don’t configure it otherwise, so somewhere along the way, I probably updated some minor package and inadvertently downloaded the patch. Woot.
Inspired by my accidental greatness, I then decided to look into patching my Windows machines, which was a lot easier than it could have been. On XP, you can download the patch, although it unfortunately requires validation. I hate ActiveX and IE, so I used the standalone validator and downloaded it.
On Win2k, though, you have to go the manual route. Fortunately, MS has made available tzedit to manually update the time zone settings, including DST boundaries. They also provide a handy guide for using it (including the correct time zone settings).
The toughest update for me was to fix the DST settings on the company palmtop computer. I had to update to ActiveSync 4.5, install the patch, and then sync the palmtop. Who knows what extra stuff the ActiveSync patch installed, which is why usually I shy away from patching unless necessary. Still, it’s done, and I guess I won’t have to worry about it until the next time the gubment gets the genius idea to extend DST a little bit instead of just making it DST year-round.