From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] bind: add support for read-only rootfs
Date: Thu, 21 Nov 2013 08:44:34 -0600 [thread overview]
Message-ID: <528E1C52.2020307@windriver.com> (raw)
In-Reply-To: <1385037621.23724.149.camel@phil-desktop.brightsign>
On 11/21/13, 6:40 AM, Phil Blundell wrote:
> On Thu, 2013-11-21 at 20:24 +0800, ChenQi wrote:
>> The purpose is to disable bind in a read-only file system by default.
>> But if user really wants it, they can set this value to 'yes'.
>
> I'm still struggling a bit to understand the reasoning here. Why would
> you install bind in the first place if you didn't want it to be enabled?
Why do people use core-image-sato, and then try to remove python?
Sorry for the snarkiness, but that's what is being avoided here.
I have to send these patches, due to the YP compliance guidelines, which is why
this is an RFC and not something I'm suggesting for the actual oe-core.. (since
the patch it depends on was not accepted.)
--Mark
> p.
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2013-11-21 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 6:59 [RFC PATCH] bind: add support for read-only rootfs Mark Hatle
2013-11-21 7:02 ` Mark Hatle
2013-11-21 12:19 ` Paul Eggleton
2013-11-21 12:12 ` Phil Blundell
2013-11-21 12:24 ` ChenQi
2013-11-21 12:40 ` Phil Blundell
2013-11-21 14:44 ` Mark Hatle [this message]
2013-11-21 18:05 ` Phil Blundell
2013-11-21 14:42 ` Mark Hatle
2013-11-21 14:51 ` Phil Blundell
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=528E1C52.2020307@windriver.com \
--to=mark.hatle@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.