Checksum: 62519
Path: utzoo!utgpu!woods
From: woods@gpu.utcs.toronto.edu (Greg Woods)
Date: Mon, 20-Feb-89 18:39:31 EST
Message-ID: <1989Feb20.183931.13918@gpu.utcs.toronto.edu>
Organization: Elegant Communications, Inc.
Newsgroups: comp.sources.bugs
Subject: Re: Flame: Problem with zoo: restoring times
References: <2884@mhres.mh.nl> <5930001@eecs.nwu.edu> <3453@sugar.uu.net> <1989Feb19.134220.29438@gpu.utcs.toronto.edu> <3465@sugar.uu.net>
Reply-To: woods@gpu.utcs.UUCP (Greg Woods)
Keywords: GMT time

In article <3465@sugar.uu.net> peter@sugar.uu.net (Peter da Silva) writes:
> In article <1989Feb19.134220.29438@gpu.utcs.toronto.edu>, woods@gpu.utcs.toronto.edu (Greg Woods) writes:
> > 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.

Let me say that another way:  store file times in zoo archives as GMT.
This will mean that zoo will be 100% compatible with Unix.  For those
machines that do not keep time interally as GMT, zoo can be compiled
locally with a given time conversion constant such that it can adjust
GMT times in archives to match local time.  Zoo need not know what time
it might be locally.  This time conversion constant would be supplied by
the person who installs zoo on a given system.  It need not be compiled
into the binary, in fact, but may come from an environment variable, a
configuration file, or some other locally convenient place.

Is there anything wrong with creating a Unix-like TZ entity on another
type of system?
-- 
						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