From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sun, 30 Jul 2006 10:18:38 -0500 From: "Eric Van Hensbergen" To: csant In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: V9FS Developers , 9fans <9fans@cse.psu.edu> Subject: [9fans] Re: Linux 9p timestamps Topicbox-Message-UUID: 93e5409e-ead1-11e9-9d60-3106f5b1d025 On 7/30/06, csant 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