@JeffW: I believe you have a couple of other ways to influence the timezone and they all revolve around the environment variable TZ.
(1) You could change TZ in the current shell, but that setting is lost as soon as the current shell terminates:
tc@box:~$ date
Tue Mar 23 20:42:16 UTC 2010
tc@box:~$ sh
tc@box:~$ TZ=CST6CDT,M3.2.0,M11.1.0
tc@box:~$ date
Tue Mar 23 15:42:39 CDT 2010
tc@box:~$ exit
tc@box:~$ date
Tue Mar 23 20:42:44 UTC 2010
tc@box:~$(2) You could amend the '.ashrc' file, this would not change the current shell, but all new shells of the current user moving forward.
tc@box:~$ echo 'TZ=CST6CDT,M3.2.0,M11.1.0' >> $HOME/.ashrc
tc@box:~$ date
Tue Mar 23 20:51:24 UTC 2010
tc@box:~$ sh
tc@box:~$ date
Tue Mar 23 15:51:29 CDT 2010
tc@box:~$ exit
tc@box:~$ date
Tue Mar 23 20:52:04 UTC 2010Please note that this change is limited to the current user and without other steps (e.g. backup of $HOME/.ashrc) will not persist. To achieve a more system wide impact, I guess changing '/etc/skel/.ashrc' might be the way to go, but it depends on your setup how this amendment will persist.
I guess it really depends on your choice of persistence. In my view for example adding a 'tz=CST6CDT,M3.2.0,M11.1.0' boot code into a GRUB stanza is a pretty simple thing to do (if you use GRUB). But you could also re-master your initrd (changing '/etc/skel/.ashrc') or the boot code in your ISO file (e.g. if using a CD-ROM to boot).
A few weeks ago I've written in another thread what I know about setting the TZ variable:
http://forum.tinycorelinux.net/index.php?topic=5017.msg27012#msg27012 This might help you further, if the appropriate value for the TZ variable appears to be a bit of a mystery.