Re: LSE conference call

From: ebiederm@xmission.com (Eric W. Biederman)
To: Scott Robert Ladd <coyote@coyotegulch.com>
Cc: John Bradford <john@grabjohn.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Hanna Linder <hannal@us.ibm.com>, jw schultz <jw@pegasys.ws>,
	lse-tech@lists.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: LSE conference call
Date: 03 May 2003 08:17:26 -0600	[thread overview]
Message-ID: <m1ade4cdxl.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3EB28FC2.6070305@coyotegulch.com>

Scott Robert Ladd <coyote@coyotegulch.com> writes:

> John Bradford wrote:
> > Ah, but assuming that you had a compass to calculate the local time
> > offset, (ignoring DST), anyway, you could have used that to calculate
> > the _local_ time without looking at your watch at all ;-).  However,
> > you wouldn't be able to calculate the timezone you were in.
> 
> Ah, but if you had a GPS system available, and a database of time zone
> boundaries, you could adjust on-the-fly for different jurisdictions. I've dones
> somethign of the sort recently for a client; the main problem lies in the
> accuracy (and size) of the database. Indiana, for example, presents unique
> challenges, with its patchwork implementation of DST...

Indiana doesn't do DST.  But it is true that people on the edges of the state
like to know what time it is for their neighbors across the border.  

I suspect the border case is at least slightly true for other places right
on the border between timezones, as well.    Though I can't think of any other
examples right now.

Eric