All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] image-live.bbclass: enable read-only-rootfs IMAGE_FEATURE
Date: Mon, 24 Jun 2013 10:48:39 +0800	[thread overview]
Message-ID: <51C7B387.2080906@windriver.com> (raw)
In-Reply-To: <92a2562fcefd5791424d47935898308b289eaf75.1371623706.git.rongqing.li@windriver.com>

On 06/19/2013 02:37 PM, rongqing.li@windriver.com wrote:
> From: "Roy.Li" <rongqing.li@windriver.com>
>
> enable read-only-rootfs to make /tmp be able to be written when using sysvinit
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
>   meta/classes/image-live.bbclass |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/meta/classes/image-live.bbclass b/meta/classes/image-live.bbclass
> index bfb59f8..3f203d1 100644
> --- a/meta/classes/image-live.bbclass
> +++ b/meta/classes/image-live.bbclass
> @@ -9,6 +9,8 @@ LABELS_append = " ${SYSLINUX_LABELS} "
>   
>   ROOTFS ?= "${DEPLOY_DIR_IMAGE}/${IMAGE_BASENAME}-${MACHINE}.ext3"
>   
> +IMAGE_FEATURES_append = " read-only-rootfs"
> +
This will result in installation of a read-only-rootfs image by default 
if we use this live image as an installer.
We should use aufs in live image. Note that the unionfs has been 
disabled for more than a year.
See https://bugzilla.yoctoproject.org/show_bug.cgi?id=4761 for more info.

Best Regards,
Chen Qi

>   do_bootimg[depends] += "${INITRD_IMAGE}:do_rootfs"
>   do_bootimg[depends] += "${PN}:do_rootfs"
>   



  reply	other threads:[~2013-06-24  2:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19  6:37 [PATCH 0/2] create /usr/lib/locale dir and enable read-only-rootfs for live image rongqing.li
2013-06-19  6:37 ` [PATCH 1/2] image-live.bbclass: enable read-only-rootfs IMAGE_FEATURE rongqing.li
2013-06-24  2:48   ` ChenQi [this message]
2013-06-19  6:37 ` [PATCH 2/2] base-files: create /usr/lib/locale dir rongqing.li

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=51C7B387.2080906@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.