From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: Re: [RFC PATCH] file as directory Date: Tue, 22 May 2007 19:26:31 -0400 Message-ID: <46537C27.4050200@cs.columbia.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org, viro@ftp.linux.org.uk, torvalds@linux-foundation.org To: Miklos Szeredi Return-path: Received: from serrano.cc.columbia.edu ([128.59.29.6]:61413 "EHLO serrano.cc.columbia.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756397AbXEVX3H (ORCPT ); Tue, 22 May 2007 19:29:07 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Miklos Szeredi wrote: > Why do we want this? > -------------------- > > That depends on who you ask. My answer is this: > > 'foo.tar.gz/foo/bar' or > 'foo.tar.gz/contents/foo/bar' > > or something similar. > > Others might suggest accessing streams, resource forks or extended > attributes through such an interface. However this patch only deals > with the non-directory case, so directories would be excluded from > that interface. here's a possibly stupid question. What about symlinks to dirs? namely the shells tend to treat them differently if postfixed with a slash or not.