All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Newall <david@davidnewall.com>
To: jaroslav.sykora@gmail.com
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Shadow directories
Date: Fri, 19 Oct 2007 06:07:45 +0930	[thread overview]
Message-ID: <4717C419.8060602@davidnewall.com> (raw)
In-Reply-To: <4717BBBB.6040205@davidnewall.com>

Jaroslav Sykora wrote:
> If anybody can think of any other solution of the "redirector problem", possibly
> even non-kernel based one, let me know and I'd be glad :-)

If I understand your problem, you wish to treat an archive file as if it 
was a directory.  Thus, in the ideal situation, you could do the following:

	cat hello.zip/hello.c
	gcc hello.zip/hello.c -o hello
	etc..


Rather than complicate matters with a second tree, use FUSE with an 
explicit directory.  For example, ~/expand could be your shadow, thus to 
compile hello.c from ~/hello.zip:

	gcc ~/expand/hello.zip^/hello.c -o hello


I think no kernel change would be required.

I'm not keen on the caret.  One of the early claims made in 
http://lwn.net/Articles/100148/ is:
> Another branch, led by Al Viro, worries about the locking 
> considerations of this whole scheme. Linux, like most Unix systems, 
> has never allowed hard links to directories for a number of reasons;

The claim is wrong.  UNIX systems have traditionally allowed the 
superuser to create hard links to directories.  See link(2) for 2.10BSD 
<http://www.freebsd.org/cgi/man.cgi?query=link&sektion=2&manpath=2.10+BSD>.  
Having got that wrong throws doubt on the argument; perhaps a path can 
simultaneously be a file and a directory.

  parent reply	other threads:[~2007-10-18 20:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 15:21 [RFC PATCH 0/5] Shadow directories Jaroslav Sykora
2007-10-18 15:22 ` [RFC PATCH 1/5] Shadow directories: headers Jaroslav Sykora
2007-10-18 15:23 ` [RFC PATCH 2/5] Shadow directories: core Jaroslav Sykora
2007-10-18 15:25 ` [RFC PATCH 3/5] Shadow directories: chdir, fchdir Jaroslav Sykora
2007-10-18 15:26 ` [RFC PATCH 4/5] Shadow directories: procfs Jaroslav Sykora
2007-10-18 15:28 ` [RFC PATCH 5/5] Shadow directories: documentation Jaroslav Sykora
2007-10-18 16:05 ` [RFC PATCH 0/5] Shadow directories Jan Engelhardt
2007-10-18 17:07   ` Jaroslav Sykora
2007-10-18 17:10     ` Jan Engelhardt
2007-10-18 20:10       ` Jaroslav Sykora
2007-10-18 20:12         ` Jan Engelhardt
     [not found]     ` <4717BBBB.6040205@davidnewall.com>
2007-10-18 20:09       ` Jan Engelhardt
2007-10-18 20:37       ` David Newall [this message]
2007-10-18 20:47         ` Al Viro
2007-10-19  2:57           ` David Newall
2007-10-19  5:37             ` Al Viro
2007-10-18 16:30 ` David Newall
2007-10-18 16:33   ` David Newall
2007-10-18 16:53     ` David Newall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4717C419.8060602@davidnewall.com \
    --to=david@davidnewall.com \
    --cc=jaroslav.sykora@gmail.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.