On Tue, Feb 27, 2007 at 03:18:33PM -0500, Steven W. Orr wrote:
I'm still running Core 4 and the new DST is coming at me like a
train. I got the latest src for Core 5: tzdata-2006p-1 and built it
installed it so I now have tzdata-2006-1 on my system.
% > rpm -q tzdata-2006p
The problem is:
% > date -d '27 March'
Tue Mar 27 00:00:00 EST 2007
Note that it says EST instead of EDT. I have no TZ variable set.
Can someone *please* tell what I have to do to fix this?
FC4 glibc didn't have /usr/sbin/tzdata-update (it was only introduced in
FC5+ and later backported to RHEL4 and RHEL3). So, after you update
package, if the changes are in your default timezone, you need to
return system-config-date or manually update /etc/localtime.
Why can't you run yum update tzdata or use up2date???
BTW, you are saying FC5 machines do not need to do anything? The new DST
is already in place? I have 2 Fedora releases in the field. FC3 and FC5.
I also have several hundred legacy 7.2 redhat machines out there with no
internet connection. Any ideas on how to fix them?