All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Colin Walters <walters@verbum.org>
Cc: poky <poky@yoctoproject.org>
Subject: Re: post-image-creation postinsts
Date: Wed, 04 May 2011 00:15:35 +0100	[thread overview]
Message-ID: <1304464535.21461.145.camel@rex> (raw)
In-Reply-To: <BANLkTi=N_hm-qCo0Gi+zoAH4mH+dszpRdA@mail.gmail.com>

On Tue, 2011-05-03 at 19:01 -0400, Colin Walters wrote:
> On Tue, May 3, 2011 at 6:36 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> >> It seems to me we could add some mechanism for mounting the image
> >> filesystem and running a script in there (guestfs?), or maybe an
> >> automated QEMU boot, run the postinsts, and sync/shutdown?
> >>
> > force the script to run on the target device. If there is a way to run
> > this at image generation time (cross safe), tell us what it is and we
> > can make it happen at image generation time!
> 
> See the bit I quoted from my original mail.  I think the most general
> solution is simply "run qemu, then shutdown", and I can look at
> automating this inside OE, but was just curious if anyone had any
> better ideas.
> 
> Would a patch to do this by default for image.bbclass make sense?

Well, we've been trying to remove the dependencies on qemu rather than
add them. I'm still not convinced we need qemu for all these cases...

Cheers,

Richard



  reply	other threads:[~2011-05-03 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 15:12 post-image-creation postinsts Colin Walters
2011-05-02 15:31 ` Mark Hatle
2011-05-03 10:36 ` Richard Purdie
2011-05-03 23:01   ` Colin Walters
2011-05-03 23:15     ` Richard Purdie [this message]
2011-05-03 23:22     ` Joshua Lock
2011-05-03 23:38       ` Mark Hatle

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=1304464535.21461.145.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=walters@verbum.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.