All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@bradfords.org.uk>
To: andrew@walrond.org (Andrew Walrond)
Cc: junkio@cox.net, linux-kernel@vger.kernel.org
Subject: Re: Symlink indirection
Date: Sun, 15 Dec 2002 12:58:14 +0000 (GMT)	[thread overview]
Message-ID: <200212151258.gBFCwEDZ000672@darkstar.example.net> (raw)
In-Reply-To: <3DFC72E4.30400@walrond.org> from "Andrew Walrond" at Dec 15, 2002 12:17:40 PM

> > "AW" == Andrew Walrond <andrew@walrond.org> gives an example of
> > a/{x,y,z}, b/{y,z}, c/z mounted on d/. in that order, later
> > mounts covering the earlier ones.
> > 
> > AW> echo "d/w" > d/w would create a new file in directory a.

I disagree.  It should create it in directory d, even though that is
the mount point.

A union mount should include files from another directory, but writes
should go to the actual named directory.

> > Back to your example; what do you wish to happen when we do
> > this?
> > 
> >     $ mv d/z d/zz && test -f d/z && cat d/z
> > 
> > Here we rename d/z (which is really c/z) to zz.  Does this
> > reveal z that used to be hidden by that, namely b/z, and "cat
> > d/z" now shows "b/z"?
> 
> Yes - exactly

Union mounts should be read only.

If read-write union mounts are needed, I don't think that we should
implement them significantly differently to the way they work in BSD.

John.

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.eib7vkv.1tju08k@ifi.uio.no>
     [not found] ` <fa.cnblikv.qjmuqd@ifi.uio.no>
2002-12-15  7:24   ` Symlink indirection junkio
2002-12-15 12:17     ` Andrew Walrond
2002-12-15 12:58       ` John Bradford [this message]
2002-12-15 14:03         ` Union mounts John Bradford
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
2002-12-23  5:58                       ` Thomas Zimmerman
2002-12-13 17:32     ` James Antill

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=200212151258.gBFCwEDZ000672@darkstar.example.net \
    --to=john@bradfords.org.uk \
    --cc=andrew@walrond.org \
    --cc=junkio@cox.net \
    --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.