9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: csant <csant@csant.info>
Cc: V9FS Developers <v9fs-developer@lists.sourceforge.net>,
	9fans <9fans@cse.psu.edu>
Subject: [9fans] Re: Linux 9p timestamps
Date: Sun, 30 Jul 2006 10:18:38 -0500	[thread overview]
Message-ID: <a4e6962a0607300818u39616e8do61ceda1047747623@mail.gmail.com> (raw)
In-Reply-To: <op.tdhmnlg0d84skq@fiore.malebolge>

On 7/30/06, csant <csant@csant.info> wrote:
> Hola,
>
> mounting a Plan 9 machine with
>         # mount -t 9p -o proto=tcp 10.0.0.5 /mnt/9/
> on a Linux box with a vanilla kernel 2.6.17.7
>
> On the Plan 9 machine:
>         % ls -l tmp/file
>         --rw-rw-r-- M 8 csant csant 1188 Jul 30 07:06 tmp/file
> and on the Linux machine:
>         $ ls -l /mnt/9/usr/csant/tmp/file
>         -rw-rw-r--  1 root root 1188 2006-07-30 13:06 /mnt/9/usr/csant/tmp/file
>
> Note that on both machines `date` gives the same, correct time. Why does
> the 9p mount give me a different time?
>

Bizarre, never noticed that before -- there is no such anomoly with
the UNIX based server (npfs anyways).   Looking at the stat(5) man
page, looks like 9p is supposed to deliver mtime and atime in terms of
GMT. It would then be the responsibility of the client to adjust for
his/her local time zone.  I don't believe we are doing that at the
moment.  I'll add it to the bug list.  Thanks.

          -eric


  reply	other threads:[~2006-07-30 15:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30  5:53 [9fans] " csant
2006-07-30 15:18 ` Eric Van Hensbergen [this message]
2006-07-30 19:48   ` [9fans] " C H Forsyth
2006-07-30 22:17     ` erik quanstrom
2006-07-31  3:20       ` Eric Van Hensbergen
2006-07-31  7:27         ` Steve Simon
2006-07-31 18:50           ` erik quanstrom
2006-07-31 19:27             ` Lluís Batlle
2006-07-31 20:24               ` csant
2006-07-31 20:57                 ` Steve Simon
2006-07-31 22:04                   ` csant
2006-07-31 22:33                     ` erik quanstrom
2006-07-31 23:06                       ` csant
2006-07-31 22:12               ` Anthony Sorace

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4e6962a0607300818u39616e8do61ceda1047747623@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=csant@csant.info \
    --cc=v9fs-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).