All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: Stephen Wille Padnos <stephen.willepadnos@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Symlink indirection
Date: Sun, 15 Dec 2002 00:41:06 +0000	[thread overview]
Message-ID: <3DFBCFA2.7030603@walrond.org> (raw)
In-Reply-To: 3DFB8B7C.10802@verizon.net

Hi steve

Stephen Wille Padnos wrote:
> 
> What would you expect to happen if you then did:
> echo "d/w" > d/w
> 
> Which physical directory would you expect a new file to go into?
> 

Using my example:

mkdir a
echo "a/x" > a/x
echo "a/y" > a/y
echo "a/z" > a/z

mkdir b
echo "b/y" > b/y

mkdir c
echo "c/z" > c/z

mkdir d
mount --bind a d
mount --bind --overlay b d
mount --bind --overlay c d

cat d/x
"a/x"

cat d/y
"b/y"

cat d/z
"c/z"

Then...

echo "d/w" > d/w would create a new file in directory a.
echo "d/y" > d/y would replace the file b/y
etc...

Is this sort of thing possible, or are there fundamental reasons that 
would make it difficult?

Andrew


  reply	other threads:[~2002-12-15  0:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 15:06 Symlink indirection Andrew Walrond
2002-12-13 15:11 ` Marc-Christian Petersen
2002-12-13 15:20   ` Andrew Walrond
2002-12-13 17:22     ` Alan Cox
2002-12-13 15:30   ` Richard B. Johnson
2002-12-13 16:17     ` James Antill
2002-12-13 16:34       ` Andrew Walrond
2002-12-13 17:24         ` James Antill
2002-12-13 16:24     ` Andrew Walrond
2002-12-13 16:26     ` Jesse Pollard
2002-12-13 15:23 ` Richard B. Johnson
2002-12-13 16:41   ` Alfred M. Szmidt
2002-12-13 16:51   ` Jeff Bailey
2002-12-13 17:15     ` Amos Waterland
2002-12-13 17:51       ` Richard B. Johnson
     [not found] ` <mailman.1039792562.8768.linux-kernel2news@redhat.com>
2002-12-13 16:16   ` Pete Zaitcev
2002-12-13 16:48     ` Andrew Walrond
2002-12-13 16:55       ` Pete Zaitcev
2002-12-13 17:04         ` Andrew Walrond
2002-12-14  5:57           ` Joseph Fannin
2002-12-14 12:47             ` Andrew Walrond
2002-12-14 13:55               ` John Bradford
2002-12-14 14:00                 ` Andrew Walrond
2002-12-14 16:13                   ` John Bradford
2002-12-14 19:50                   ` Stephen Wille Padnos
2002-12-15  0:41                     ` Andrew Walrond [this message]
2002-12-23  5:58                       ` Thomas Zimmerman
2002-12-13 17:32     ` James Antill
     [not found] <fa.eib7vkv.1tju08k@ifi.uio.no>
     [not found] ` <fa.cnblikv.qjmuqd@ifi.uio.no>
2002-12-15  7:24   ` junkio
2002-12-15 12:17     ` Andrew Walrond
2002-12-15 12:58       ` John Bradford

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=3DFBCFA2.7030603@walrond.org \
    --to=andrew@walrond.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen.willepadnos@verizon.net \
    /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.