🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.misc
Article #21

Re: US/Pacific-New didn't change to PST last Sunday

#21
From: Mike Carlton
Date: Tue, 27 Oct 1992 20:49
51 lines
2866 bytes
In article <1ck55uINNg7@darkstar.UCSC.EDU> isbell@cats.ucsc.edu (Art Isbell)  
writes:
> 
> Did anyone else experience the failure of US/Pacific-New to change to PST
> correctly?   I set Preferences to US/Pacific and that seems to work, but will
> it work next spring?  Which is the proper Preferences setting for those of us
> in the US/Pacific time zone?
> -- 
> 

You should be using US/Pacific.  The following explanation is from the
most recent Comp.risks (13.87).

cheers,
--mike (carlton@cs.berkeley.edu)

-----------------------------------------------------------------------------

Date: Mon, 26 Oct 92 14:47:57 PST
From: eggert@twinsun.com (Paul Eggert)
Subject: US presidential election year politics help cause time zone bugs

Several people on the west coast of the US reported that their Unix
systems failed to switch from daylight savings time to standard time
yesterday, 26 October 1992.  The reason?  When they originally
configured their systems, they were asked to choose one of the
following time zone rules:

	US/Alaska	US/Central	US/Hawaii	US/Pacific
	US/Aleutian	US/East-Indiana	US/Michigan	US/Pacific-New
	US/Arizona	US/Eastern	US/Mountain	US/Samoa
	...

Some people chose `US/Pacific-New' instead of `US/Pacific'.
After all, who wants the old version when you can have the new version?

Unfortunately, `US/Pacific-New' stands for ``Pacific Presidential Election
Time'', which was passed by the House in April 1989 but never signed into law.
In presidential election years, this rule would have delayed the PDT-to-PST
switchover until after the election, to lessen the effect of broadcast news
election projections on last-minute west-coast voters.  Thus, US/Pacific-New
and US/Pacific have always been identical -- until yesterday.

This problem comes from combining Arthur David Olson's deservedly popular time
zone software (which you can FTP from elsie.nci.nih.gov in pub/tz92b.tar.Z)
with some overly terse vendor-supplied installation procedures.  No doubt Olson
did not use a more informative name like `US/Pacific-Presidential-Election'
because of the 14-character file name length limit in many Unix file systems.
In view of yesterday's experience, though, it seems unwise to make the
hypothetical choice available under any name, since it gives free rein to
Murphy's Law.
Technical Details
Message-ID: <1cka1fINNl59@agate.berkeley.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!kithrup!hoptoad!pacbell.com!sgiblab!spool.mu.edu!agate!agate!usenet
References: <1ck55uINNg7@darkstar.UCSC.EDU>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!kithrup!hoptoad!pacbell.com!sgiblab!spool.mu.edu!agate!agate!usenet
From: carlton@cs.berkeley.edu (Mike Carlton)
Newsgroups: comp.sys.next.misc
Subject: Re: US/Pacific-New didn't change to PST last Sunday
Date: 27 Oct 1992 20:49:51 GMT
Organization: University of California, Berkeley
Lines: 51
Distribution: usa
Message-ID: <1cka1fINNl59@agate.berkeley.edu>
References: <1ck55uINNg7@darkstar.UCSC.EDU>
Reply-To: carlton@cs.berkeley.edu
NNTP-Posting-Host: peets.berkeley.edu