From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: unable to copy directory recursively to a vfat partition Date: Thu, 24 Jul 2008 09:23:22 -0400 Message-ID: <87prp3a01h.fsf@stupidchicken.com> References: <20080723185150.txs6e4gbr23ow0g4@webmail.mit.edu> <87zlo7zw5u.fsf@gmx.de> <87tzefzv2b.fsf@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1216905837 12501 80.91.229.12 (24 Jul 2008 13:23:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 24 Jul 2008 13:23:57 +0000 (UTC) Cc: emacs-devel@gnu.org To: Sven Joachim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 24 15:24:46 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KM0o3-0001r0-8t for ged-emacs-devel@m.gmane.org; Thu, 24 Jul 2008 15:24:31 +0200 Original-Received: from localhost ([127.0.0.1]:43113 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KM0n9-0005tS-P2 for ged-emacs-devel@m.gmane.org; Thu, 24 Jul 2008 09:23:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KM0n5-0005t6-5k for emacs-devel@gnu.org; Thu, 24 Jul 2008 09:23:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KM0n3-0005sg-5v for emacs-devel@gnu.org; Thu, 24 Jul 2008 09:23:30 -0400 Original-Received: from [199.232.76.173] (port=59794 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KM0n3-0005sX-1m for emacs-devel@gnu.org; Thu, 24 Jul 2008 09:23:29 -0400 Original-Received: from c-24-63-201-57.hsd1.ma.comcast.net ([24.63.201.57]:16997 helo=furry) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KM0n2-0002pw-Ug for emacs-devel@gnu.org; Thu, 24 Jul 2008 09:23:29 -0400 Original-Received: by furry (Postfix, from userid 1000) id 9795DC058; Thu, 24 Jul 2008 09:23:22 -0400 (EDT) In-Reply-To: <87tzefzv2b.fsf@gmx.de> (Sven Joachim's message of "Thu, 24 Jul 2008 07:54:04 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101381 Archived-At: Sven Joachim writes: > On 2008-07-24 07:30 +0200, Sven Joachim wrote: > >> I do have access to vfat, but I cannot reproduce the bug. IIRC there >> was some change in Linux 2.6.25 that caused the chmod call to report >> failure (it never works on vfat anyway, but that used to be silently >> ignored). This change seems to have been reverted in the meantime, >> though; I'm running 2.6.26 here. > > The change in 2.6.25 also broke rsync, as can be seen on > https://bugzilla.redhat.com/show_bug.cgi?id=449080. I'll have a look at > the problem when I get around to reboot with a 2.6.25 kernel. Does anyone know what the BSDs do? In other words, is reporting failure for chmod simply "undefined behavior" that is up to the discretion of the kernel (i.e., we need to be able to handle it), or is it simply a Linux bug (i.e., we can probably get away with doing nothing)?