From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Robert Yang <liezhi.yang@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] linux-yocto 4.4: enable overlayfs by default
Date: Sun, 03 Apr 2016 22:46:39 +0100 [thread overview]
Message-ID: <1459719999.7348.142.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4NVbCvZwHt62hZzrV+NLpq0qytN_duRv8EigM12mUJs7g@mail.gmail.com>
On Sun, 2016-04-03 at 06:11 -0400, Bruce Ashfield wrote:
>
>
> On Sun, Apr 3, 2016 at 5:58 AM, Robert Yang <
> liezhi.yang@windriver.com> wrote:
> > So that iso can work well, otherwise the iso is readonly and there
> > would
> > be errors. The other way is aufs, but overlayfs is more pupolar and
> > had
> > been merged by kernel mainline, we need make iso work well by
> > default.
> Nope. As I mentioned before, this can't be a always on default. It
> will conflict
> with other unionFS use cases.
>
> If you want overlayfs enabled, it needs to be triggered from a
> specific image
> or distro feature.
We can't change the kernel config from an image so it would have to be
a distro setting. Is there a problem with enabling both as modules btw?
I assume they can coexist?
Cheers,
Richard
next prev parent reply other threads:[~2016-04-03 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 9:58 [PATCH 0/1 V2] linux-yocto 4.4: enable overlayfs by default Robert Yang
2016-04-03 9:58 ` [PATCH 1/1] " Robert Yang
2016-04-03 10:11 ` Bruce Ashfield
2016-04-03 21:46 ` Richard Purdie [this message]
2016-04-03 23:56 ` Bruce Ashfield
2016-04-05 1:53 ` Robert Yang
2016-04-05 2:31 ` Bruce Ashfield
2016-04-05 2:48 ` Robert Yang
2016-04-05 6:33 ` Bruce Ashfield
2016-04-05 6:42 ` Robert Yang
2016-04-05 8:33 ` Bruce Ashfield
2016-04-05 9:06 ` Robert Yang
2016-04-05 14:59 ` Bruce Ashfield
2016-04-03 10:00 ` [PATCH 0/1 V2] " Robert Yang
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=1459719999.7348.142.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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.