Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

time change



Seth Gordon <seth at genome.wi.mit.edu> writes:

> Nathan Meyers wrote:
> > 
> > On Fri, Sep 20, 2002 at 03:01:02PM -0400, Rob Ransbottom wrote:
> > > On 19 Sep 2002, Derek Atkins wrote:
> > >
> > > > usually the way to solve this problem is to keep the system
> > > > clock in "local" time and set linux to know that the system is
> > > > in local, not utc, time.
> > >
> > > For no compelling reason I've always wanted to set my clocks to
> > > UTC.

There is a good reason they invented UTC in the first place - you
always know when an event occurred relative to some other event,
e.g. 8 am EST is after, not before 10 am CET. Consequently, when your
files move from one timezone to another (because you took your laptop
to Europe or because you emailed a file to the other coast) you still
know which file is older.

> > > Can the various Window OS deal with this?
> > 
> > No.
> 
> Move to England?

Umm, that would only work half the year... they have DST, too. Now
Iceland *is* GMT year round, so that might work better.

Ari (aka ari at cogsci.ed.ac.uk)





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org