On Sun, 15 Dec 2002 00:41:06 +0000
Andrew Walrond <andrew@walrond.org> wrote:
> 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...
I would have expected any changes to /d/* to happen in c; as that was
the *last* change to the mount point. It would allow much niceness, like
NFS root with local changes having persistence, if you "mount -bind
-overlay <smaller local drive> /"
> Is this sort of thing possible, or are there fundamental reasons that
> would make it difficult?
I'll leave that to greater minds then mine. :)
> Andrew
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Dec 23 2002 - 22:00:31 EST