From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Woodhouse Subject: Re: Fallthrus as full-length symlinks? Date: Wed, 25 Nov 2009 09:43:32 +0000 Message-ID: <1259142212.32238.66.camel@macbook.infradead.org> References: <20091113174631.GD19656@shell> <30797.1258523235@jrobl> <20091125021509.GF21724@shell> <32549.1259116563@jrobl> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Valerie Aurora , linux-fsdevel@vger.kernel.org, Alexander Viro , Jan Blunck , Christoph Hellwig , Andy Whitcroft , Scott James Remnant , Sandu Popa Marius , Jan Rekorajski , Arnd Bergmann , Vladimir Dronnikov , Felix Fietkau To: hooanon05@yahoo.co.jp Return-path: Received: from casper.infradead.org ([85.118.1.10]:38244 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751392AbZKYJnq (ORCPT ); Wed, 25 Nov 2009 04:43:46 -0500 In-Reply-To: <32549.1259116563@jrobl> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, 2009-11-25 at 11:36 +0900, hooanon05@yahoo.co.jp wrote: > > No, that is not what I mean. > When a fallthru entry is implemented as a kind of a symlink, what will > they look like via /proc/pid/{fd,maps,cwd,exe}? In that respect, and many others, it would behave more like a cross-device hardlink than a symlink. In fact, I was originally thinking that it would have something like an nfsfh for the target inode, rather than a device (or fsid?) and pathname. -- David Woodhouse Open Source Technology Centre David.Woodhouse@intel.com Intel Corporation