Path: utzoo!attcan!utgpu!woods
From: woods@gpu.utcs.toronto.edu (Greg Woods)
Newsgroups: comp.sources.bugs
Subject: Re: Flame: Problem with zoo: restoring times
Summary: standard times
Keywords: GMT time
Message-ID: <1989Feb19.134220.29438@gpu.utcs.toronto.edu>
Date: 19 Feb 89 18:42:20 GMT
References: <2884@mhres.mh.nl> <5930001@eecs.nwu.edu> <3453@sugar.uu.net>
Reply-To: woods@gpu.utcs.Toronto.EDU (Greg Woods)
Organization: Elegant Communications, Inc.
Lines: 20
Checksum: 44373

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 (an idea I absolutely detest) or that you cannot
replace enough of your O/S to fool yourself into thinking you have your
machine running on GMT (for example, on a PC use the MKS toolkit which
properly handles TZ)?  I suggest that zoo archives (another thing I find
very little use for) 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.
-- 
						Greg Woods.

{utgpu,lsuc!gate,ontmoh}!woods, woods@{gpu.utcs.Toronto.EDU,utorgpu.BITNET}
1-416-443-1734 [h], 1-416-595-5425 [w]   LOCATION: Toronto, Ontario, Canada