Hi--
I doubt any version of 10.3.9 is aware of the changes, certainly the non-server version isn't. I've updated the
zoninfo database on a couple of my regular 10.3.9 machines. According to my notes, the Finder display is off, but it's so long ago that I noticed it, I don't remember what I meant by that. I didn't worry too much about it, since I figured I'd be running Tiger for sure on all my machines by then.
Here's a step by step procedure if you'd like to try updating it. First, open the Terminal window and copy the old zoneinfo folder to your desktop as a backup:
<pre class="command">sudo cp -r /usr/share/zoneinfo ~/Desktop/</pre>Now, make another directory on your desktop to hold a downloaded file:
<pre class="command">mkdir ~/Desktop/newzoneinfo</pre>Go to
ftp://elsie.nci.nih.gov/pub/ and look for a file called "
tzdataYYYYr.tar.gz". Note that the YYYY is the year of the revision and "r" is a letter revision indicator. The one I just downloaded is called "
tzdata2006n.tar.gz." By the time you download it, there could be another revision. Put this file in your
newinfo directory on the Desktop. Now change to that directory and extract the files:
<pre class="command">cd ~/Desktop/newzoneinfo/
tar -zxvf tzdata2006n.tar.gz</pre>Now compile and install the new time zones:
<pre class="command">sudo zic -v africa antarctica asia australasia \
europe northamerica southamerica pacificnew \
etcetera factory backward systemv solar87 solar88 solar89</pre>Just copy and paste that into the Terminal window, backslashes and all if you want. Once you hit the "enter" key, you'll be asked to provide your administrator's password. It'll take a few seconds, and you should get back a command prompt without any errors printed out.
You can test it with this command:
<pre class="command">zdump -v /usr/share/zoneinfo/America/Denver | grep 2007</pre>You should see the changes for 2007 reflected there. Another test you can use is a Perl one-liner:
<pre class="command">perl -e 'use POSIX qw(strftime); print strftime("%Y-%m-%d %r %Z\n", localtime(86400*13586));'</pre>Just change the last number (13586) by addition or subtraction to zero in on the time change. I haven't noticed any bad side effects from doing this, but I'd suggest trying it on a non-production machine first, if you can...
charlie