From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Pawel Dziepak" Subject: Re: utimes() with vfat is problematic Date: Tue, 10 Jul 2007 18:54:35 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, "Linux Kernel Mailing List" , hirofumi@mail.parknet.co.jp To: "Jan Engelhardt" Return-path: Received: from mu-out-0910.google.com ([209.85.134.188]:5707 "EHLO mu-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754714AbXGJQyi (ORCPT ); Tue, 10 Jul 2007 12:54:38 -0400 Received: by mu-out-0910.google.com with SMTP id i10so1492800mue for ; Tue, 10 Jul 2007 09:54:36 -0700 (PDT) In-Reply-To: Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 7/10/07, Jan Engelhardt wrote: > Linux does check for write permission, but _only_ for time=NULL. > Hence it would be helpful if someone knows the exact SUS text, > or whether this is not explicitly specified in SUS, leaving room > for interpretation. I have already checked it strictly. This "problem" occurs not only on vfat partitions. You can *not* do uptime() for time!=NULL if you are not a file owner. So, everything in Linux is correct. It is not possible to solve your problem without changing SUS, it is not even a problem... I made mistake in my first post, because I was too implied by piece of code that you've quoted. Pawel