From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: NeilBrown <neilb@suse.de>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, apw@canonical.com, nbd@openwrt.org,
hramrach@centrum.cz, Miklos Szeredi <mszeredi@suse.cz>
Subject: Re: [PATCH 6/6] overlay: overlay filesystem documentation
Date: Tue, 19 Apr 2011 13:13:53 +0900 [thread overview]
Message-ID: <6291.1303186433@jrobl> (raw)
In-Reply-To: <20110419135818.024cd289@notabene.brown>
NeilBrown:
> Only to top level of an overlay stack is writable. All others are or should
> be read only. So only the top level can change.
>
> So in your example, fileA will be copied from ro1 directly into rwN where it
> will then be appended to.
I see.
When I have time, I will try building overlayfs.
Thank you.
J. R. Okajima
next prev parent reply other threads:[~2011-04-19 4:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 16:00 [PATCH 0/6] overlay filesystem Miklos Szeredi
2011-04-18 16:00 ` [PATCH 1/6] vfs: add i_op->open() Miklos Szeredi
2011-04-18 16:00 ` [PATCH 2/6] vfs: export do_splice_direct() to modules Miklos Szeredi
2011-04-18 16:00 ` [PATCH 3/6] vfs: introduce clone_private_mount() Miklos Szeredi
2011-04-18 16:00 ` [PATCH 4/6] overlay filesystem Miklos Szeredi
2011-04-18 16:00 ` [PATCH 5/6] overlayfs: add statfs support Miklos Szeredi
2011-04-18 16:00 ` [PATCH 6/6] overlay: overlay filesystem documentation Miklos Szeredi
2011-04-19 3:05 ` J. R. Okajima
2011-04-19 3:58 ` NeilBrown
2011-04-19 4:13 ` J. R. Okajima [this message]
2011-04-18 18:19 ` [PATCH 0/6] overlay filesystem Michal Suchanek
2011-04-19 9:39 ` Miklos Szeredi
2011-04-19 9:43 ` [PATCH 1/2] ovl: fix missing include Miklos Szeredi
2011-04-19 9:43 ` [PATCH 2/2] ovl: fix building as a module Miklos Szeredi
2011-05-09 19:14 ` [PATCH 0/6] overlay filesystem Michal Suchanek
2011-05-10 16:30 ` Miklos Szeredi
-- strict thread matches above, loose matches on Subject: below --
2010-09-03 13:41 [PATCH 0/6] overlay filesystem prototype Miklos Szeredi
2010-09-03 13:41 ` [PATCH 6/6] overlay: overlay filesystem documentation Miklos Szeredi
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=6291.1303186433@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=apw@canonical.com \
--cc=hramrach@centrum.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=mszeredi@suse.cz \
--cc=nbd@openwrt.org \
--cc=neilb@suse.de \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).