[lkml]   [2003]   [May]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: LSE conference call
Followup to:  <>
By author: (Eric W. Biederman)
In newsgroup:
> Scott Robert Ladd <> 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.

Part of Indiana does DST, part of it doesn't. In particular, the
parts of Indiana is in the CT timezone (Gary area) *does* do DST.


<> at work, <> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:35    [W:0.042 / U:1.692 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site