Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!mit-eddie!rutgers!bellcore!texbell!uhnix1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sources.bugs
Subject: Re: Flame: Problem with zoo: restoring times
Keywords: GMT time
Message-ID: <3465@sugar.uu.net>
Date: 19 Feb 89 21:41:50 GMT
References: <2884@mhres.mh.nl> <5930001@eecs.nwu.edu> <3453@sugar.uu.net> <1989Feb19.134220.29438@gpu.utcs.toronto.edu>
Organization: Sugar Land Unix - Houston, TX
Lines: 26

In article <1989Feb19.134220.29438@gpu.utcs.toronto.edu>, woods@gpu.utcs.toronto.edu (Greg Woods) writes:
> In article <3453@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
> > In article <5930001@eecs.nwu.edu>, gore@eecs.nwu.edu (Jacob Gore) writes:
> > > For those systems, is there any harm in pretending that they *are* on GMT?

> > Sure. I zoo up an archive on my Amiga, and unzoo it on a UNIX box. All the
> > times are now off.

> What would be a better solution, provided you absolutely must run your
> machine on local time ...

Distasteful, but true fact: most operating systems other than UNIX do this.

> I suggest that zoo archives (another thing I find very little use for)

So why do you care?

> store GMT internally, and for those O/S's that
> can't manage to relate to the rest of the world, zoo may be compiled
> with a local time conversion factor built in.

Because zoo doesn't know what the local time is, but the UNIX system does
have everythink it needs to convert between GMT and local time. QED.
-- 
Peter "Have you hugged your wolf today" da Silva  `-_-'  Hackercorp.
...texbell!sugar!peter, or peter@sugar.uu.net      'U`