From mboxrd@z Thu Jan 1 00:00:00 1970 From: hooanon05@yahoo.co.jp Subject: Re: [PATCH 15/32] union-mount: Documentation Date: Mon, 25 May 2009 17:43:10 +0900 Message-ID: <7294.1243240990@jrobl> References: <1242662968-11684-1-git-send-email-jblunck@suse.de> <1242662968-11684-16-git-send-email-jblunck@suse.de> <8417.1243232743@jrobl> <200905250903.08165.arnd@arndb.de> Cc: Jan Blunck , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, bharata@in.ibm.com, dwmw2@infradead.org, mszeredi@suse.cz, vaurora@redhat.com To: Arnd Bergmann Return-path: Received: from mtoichi12.ns.itscom.net ([219.110.2.182]:46506 "EHLO mtoichi12.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755313AbZEYInw (ORCPT ); Mon, 25 May 2009 04:43:52 -0400 In-Reply-To: <200905250903.08165.arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Arnd Bergmann: > Right, but that is consistent with how the kernel would treat a > rename from one mount point to another, and tools like 'mv' > can handle this in user space. Yes, that is the description in the union mount document. While it says to rename a regular file is implemented, the code differs actually. ---------------------------------------- +Rename across different levels of the union is implemented as a copy-up +operation for regular files. Rename of directories simply returns EXDEV, the +same as if we tried to rename across different mounts. Most applications have ::: ----------------------------------------