"Permanent" DST

Owen DeLong owen at delong.com
Wed Mar 16 17:29:07 UTC 2022

> On Mar 15, 2022, at 15:05 , Jan Schaumann via NANOG <nanog at nanog.org> wrote:
> Dave <dedelman at iname.com> wrote:
>> Folks for most systems, this is a change to a single file. Not a really hard thing to accomplish
> Oh, hah, good one.
> I twitch with mild PTSD thinking about the last time
> there was change to DST in the US[1], and how
> everybody quickly found out that e.g., Java,
> databases, programming languages, etc. often ship
> their own (poorly kept up to date) zonefiles different
> from the OS's, and that was before un-updatedable IoT
> systems became ubiquitous.
> Change to a single file my foot.

You’re right… Two changes to a single file in most cases:

1.	Set the correct new timezone (e.g. MST for California).
2.	Turn off the Daylight Stupid Time flag.

The previous change involved updating MANY zone files to change when DST happened.

This change eliminates that complexity altogether.

This is a MUCH simpler change than the previous one.


More information about the NANOG mailing list