All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: RFC: meta-ro-rootfs approach and volatiles vs tmpfiles.d
Date: Wed, 31 Jul 2013 15:09:25 +0800	[thread overview]
Message-ID: <51F8B825.3000707@windriver.com> (raw)
In-Reply-To: <CABcZANk_XvT3uHDQQmqsm-4dTVZYd-D3RRsW+wz=2cdE-xkbmA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

On 07/31/2013 02:53 AM, Chris Larson wrote:
> On Wed, Jul 24, 2013 at 7:51 PM, ChenQi <Qi.Chen@windriver.com 
> <mailto:Qi.Chen@windriver.com>> wrote:
>
>     You can get more information from the bug link below. The related
>     bugs are listed in the blocks list of this bug.
>     https://bugzilla.yoctoproject.org/show_bug.cgi?id=4103
>     You can also review the patchset for these bugs on
>
>     http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/read-only-rootfs-in-live-images
>
>
> I'll start playing around with this locally, to see how well it'd work 
> (with adjustments to support systemd) for our use cases, and will go 
> from there on our end. Up next for me:
>

Thank you very much for your review :)

Best Regards,
Chen Qi

> - see if your r/o bits will be suitable for us with systemd rather 
> than using our tmpfiles override mechanism. we need to support this on 
> much more than just live images, and we need systemd :)
> - pursue systemd support for services missing that support in oe-core
> - pursue improved sysvinit / systemd feature parity, and potential 
> volatiles -> tmpfiles migration / consolidation
> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics


[-- Attachment #2: Type: text/html, Size: 3157 bytes --]

      reply	other threads:[~2013-07-31  7:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24 18:54 RFC: meta-ro-rootfs approach and volatiles vs tmpfiles.d Chris Larson
2013-07-24 21:47 ` Colin Walters
2013-07-24 22:43   ` Chris Larson
2013-07-24 21:51 ` Otavio Salvador
2013-07-24 22:34   ` Chris Larson
2013-07-24 22:39     ` Otavio Salvador
2013-07-24 22:40     ` Otavio Salvador
2013-07-24 22:55       ` Chris Larson
2013-07-25  2:51 ` ChenQi
2013-07-30 18:17   ` Chris Larson
2013-07-30 18:22     ` Chris Larson
2013-07-30 18:26     ` Chris Larson
2013-07-30 20:19       ` Paul Eggleton
2013-07-31  7:07     ` ChenQi
2013-07-30 18:53   ` Chris Larson
2013-07-31  7:09     ` ChenQi [this message]

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=51F8B825.3000707@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=clarson@kergoth.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.