From: "André Draszik" <git@andred.net>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version)
Date: Thu, 01 Dec 2016 10:26:03 +0000 [thread overview]
Message-ID: <1480587963.13682.12.camel@andred.net> (raw)
In-Reply-To: <1480578170.6873.312.camel@intel.com>
On Thu, 2016-12-01 at 08:42 +0100, Patrick Ohly wrote:
> On Wed, 2016-11-30 at 17:19 +0000, André Draszik wrote:
> > I liked swupd for its ability to be used both for initial provisioning
>
> You mean installing from the update repository? That's something that
> Clear Linux OS can do with their installer, but nothing like that has
> been tried with a Yocto-based build. That doesn't mean that it can't be
> done, it's just work.
Yes. In our case we can only provision the NOR flash in the factory (which
is too small for the real file system), so I have the swupd-client inside a
small initramfs in NOR flash, and from there I can provision NAND flash
using swupd verify -i
All yocto based, but in its current state not in a generally useful shape
for a wider audience.
> > as
> > well as for incremental updates. The latter being important when you
> > have
> > *loads* of devices, where it doesn't seem to make sense to download a
> > full
> > image for a tiny change to each device (think cellular!),
>
> That's indeed one of the strengths of swupd. OSTree comes close in terms
> of some key characteristics (file-based, persistent /etc and /var). It
> would be interesting to know how efficient updating via OSTree is.
True.
A.
next prev parent reply other threads:[~2016-12-01 10:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:03 [meta-swupd][PATCH] bsdiff: update to latest version André Draszik
2016-11-30 11:04 ` Patrick Ohly
2016-11-30 14:31 ` André Draszik
2016-11-30 14:59 ` update mechanisms (was: Re: [meta-swupd][PATCH] bsdiff: update to latest version) Patrick Ohly
2016-11-30 17:19 ` André Draszik
2016-12-01 7:42 ` Patrick Ohly
2016-12-01 10:26 ` André Draszik [this message]
2016-12-01 11:25 ` Patrick Ohly
2016-12-06 9:01 ` update mechanisms Stefano Babic
2016-12-06 9:45 ` Patrick Ohly
2016-12-06 14:11 ` Lopez, Mariano
2016-12-06 18:45 ` Philip Balister
2016-12-06 22:38 ` Stefano Babic
2016-12-07 7:05 ` Kristian Amlie
2016-12-09 15:13 ` Patrick Ohly
2016-12-09 16:03 ` Stefano Babic
2016-12-12 14:59 ` Mariano Lopez
2016-12-12 15:41 ` Patrick Ohly
2016-12-12 15:49 ` Mariano Lopez
2016-12-12 19:02 ` Patrick Ohly
2016-12-13 14:03 ` Lopez, Mariano
2016-12-12 6:39 ` Kristian Amlie
2017-03-02 0:35 ` Eystein Måløy Stenberg
2017-03-10 13:02 ` Patrick Ohly
2017-03-10 13:35 ` Kristian Amlie
2017-03-10 14:20 ` Patrick Ohly
2016-12-13 8:51 ` Mike Looijmans
2016-12-13 9:08 ` Patrick Ohly
2016-12-12 15:13 ` André Draszik
2016-12-12 15:32 ` Patrick Ohly
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=1480587963.13682.12.camel@andred.net \
--to=git@andred.net \
--cc=patrick.ohly@intel.com \
--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.