From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a4e6962a0607302020w2a9c6c01ia191191698a81b59@mail.gmail.com>
Date: Sun, 30 Jul 2006 22:20:02 -0500
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Linux 9p timestamps
In-Reply-To: <527cb238df9a41e8b1649fcacb723f94@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <56b41a6171559105afdf0220bc23e55e@vitanuova.com>
	<527cb238df9a41e8b1649fcacb723f94@quanstro.net>
Topicbox-Message-UUID: 945563a6-ead1-11e9-9d60-3106f5b1d025

On 7/30/06, erik quanstrom <quanstro@quanstro.net> wrote:
> yes.  unix and plan 9 both use seconds since epoch to
> represent the date and both use an epoch defined in the
> GMT timezone.
>
> there shouldn't be any conversion required as the timezone+dst
> offset needs to be added only for display.
>
> - erik
>
> On Sun Jul 30 14:51:52 CDT 2006, forsyth@vitanuova.com wrote:
> > >It would then be the responsibility of the client to adjust for
> > >his/her local time zone.
> >
> > isn't the value of ctime and mtime always in gmt, even on linux?
> > on unix it was only the programs calling ctime (or relatives)
> > that finally adjusted for local time, typically before displaying it.
> > i don't see how the client kernel would or should get involved.
>

okay - I'll bite -- so what's csant's problem then?

          -eric