All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Deploying Yocto build images
Date: Thu, 21 Nov 2013 13:10:46 +0100	[thread overview]
Message-ID: <528DF846.9050306@denx.de> (raw)

Hi everybody,

in the last ELCE, David point out in his presentation that we should
improve how to deploy Yocto images on the target.

I did some work this year to provide a reliable way for some customers
of us to install Yocto's images in field, and I have published last week
the sources. Here the link of the announcement:

	http://comments.gmane.org/gmane.comp.embedded.eldk/2397

Mainly, it is a tool that can be stored in the rootfs or will be put in
a separate initrd image and whose goal is only to update the system. I
have tried to describe pros and cons of several different solutions
(updating via bootloader ? single copy against dual copy ?) - you can
find details in the doc directory in the swupdate repository.

Maybe someone of you can find this helpful, and I will be happy if I
could get some feedback.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


             reply	other threads:[~2013-11-21 12:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 12:10 Stefano Babic [this message]
2013-11-21 12:34 ` Deploying Yocto build images Diego Sueiro
2013-11-21 13:15   ` Stefano Babic
2013-11-21 18:20   ` Michael_E_Brown
2013-11-21 18:49     ` Stefano Babic
2013-11-21 15:48 ` Bryan Evenson
2013-11-21 17:08   ` Stefano Babic

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=528DF846.9050306@denx.de \
    --to=sbabic@denx.de \
    --cc=yocto@yoctoproject.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.