All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] bind: add support for read-only rootfs
Date: Thu, 21 Nov 2013 20:24:40 +0800	[thread overview]
Message-ID: <528DFB88.5080404@windriver.com> (raw)
In-Reply-To: <1385035973.23724.146.camel@phil-desktop.brightsign>

On 11/21/2013 08:12 PM, Phil Blundell wrote:
> On Thu, 2013-11-21 at 00:59 -0600, Mark Hatle wrote:
>> +# When using a read-only rootfs additional setup may be required
>> +# uncomment the following line to make bind start in read-only rootfs
>> +#ALLOW_ROOTFS_READ_ONLY="yes"
> If the filesystem is read-only then it's going to be fairly difficult
> for the user to uncomment this line on the target.

Hi Phil,

I think the user can remount it read-write or just do it at rootfs time.

> Why would you ever want this variable to be set to anything other than
> "yes"?  If your filesystem is not in fact read-only then it isn't going
> to have any effect, and if your filesystem is read-only then bind won't
> work without it.

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'.

>> ++	[ `is_on_read_only_partition /etc/bind` = "yes" ] && bind_mount /var/volatile/bind/etc /etc/bind
>> ++	[ `is_on_read_only_partition /var/named` = "yes" ] && bind_mount /var/volatile/bind/named /var/named
> Is it really necessary to mount a tmpfs at /etc/bind?  Can't those files
> just be relocated somewhere else?

I'm afraid not. At least I don't know how.

Best Regards,
Chen Qi

> p.
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>



  reply	other threads:[~2013-11-21 12:24 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 [this message]
2013-11-21 12:40     ` Phil Blundell
2013-11-21 14:44       ` Mark Hatle
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=528DFB88.5080404@windriver.com \
    --to=qi.chen@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.