mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Taimir Aguacil <taimir.aguacil@trapezegroup.com>
To: Enrico Joerns <ejo@pengutronix.de>
Cc: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] RAUC
Date: Tue, 30 Oct 2018 11:27:44 +0000	[thread overview]
Message-ID: <1540898865079.67025@trapezegroup.com> (raw)
In-Reply-To: <17606887-d5b4-c456-7783-bf813b35341b@pengutronix.de>

Hi Enrico, 

Thank you for your detailed answer. This clarified some confusions. 

How do I subscribe to the mailing list ? 

BR 
Taimir 
________________________________________
From: Enrico Joerns <ejo@pengutronix.de>
Sent: Tuesday, October 30, 2018 8:39 AM
To: Taimir Aguacil
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] RAUC

Hi Taimir,

On 10/29/18 11:27 AM, Taimir Aguacil wrote:
> Dear RAUC team,
>
> I attended the embedded Linux conference, and got to know you and see your demo there!
>
> There were still some few open questions that I am putting in this email. It would be very helpful to get the answers.
>
> Right now bundle and network modes are supported, is an update over USB supported ? If not, are there any plans to do so ?

maybe this needs some clarification: 'Bundle' is the data/archive format that we use for packing or unpacking the update artifacts and meta information.
This is not tied to any update *source*, which (potentially) could be quite everything from a µSD Card, over a USB stick to a network upload or whatever.

The real 'network mode' you might refer to, is deprecated in RAUC and will not gain further development.
This in fact was a 'non-bundle mode' using a signed manifest and requiring to download the install artifacts separately from a server.

However, this does not limit usage over network. Rather, it has been replaced by the more powerful usage of casync for chunked delta-like downloads.

In most cases the right way to go is to let an independent unit handle the provisioning of the bundle, e.g. by mounting a USB stick, downloading a file over network / internet, or whatever,
and then trigger RAUC (using D-Bus or CLI) with the path tho this (local or remote) bundle and let it do the rest of the work.

We have some examples code for some scenarios, e.g. for using a CGI or interacting with hawkbit, but our opinion is that the bundle source handling is quite use-case specific.

> Furthermore, for an update over the air (Using cellular or WLAN), is it possible ? Or do I need to include a mechanism for the bundle download and then use the bundle mode where the bundle is on a partition ?

This basically picks up the same questions I hopefully answered on the previous question already.
In general, when you download an update, there are two options: (1) either you need to have some temporary storage for the entire artifact (e.g. a data partition, or RAM) or (2) you can stream the data directly into your target device / partition.
The latter is what casync bundles [1][2] offer you.

Also note that when using tar and compression the downloaded image might be much smaller than the actual partition it should be installed to.


I hope that answers your question. Please also consider subscribing to this Mailing list as, by default, it does not allow non-members to post questions (to prevent Spam).


Best regards,
Enrico


[1] https://rauc.readthedocs.io/en/latest/advanced.html#rauc-casync-support
[2] http://0pointer.net/blog/casync-a-tool-for-distributing-file-system-images.html

--
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
RAUC mailing list

  reply	other threads:[~2018-10-30 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 10:27 Taimir Aguacil
2018-10-30  7:39 ` Enrico Joerns
2018-10-30 11:27   ` Taimir Aguacil [this message]
2018-10-30 11:42     ` Enrico Joerns

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=1540898865079.67025@trapezegroup.com \
    --to=taimir.aguacil@trapezegroup.com \
    --cc=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox