From: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
To: rauc@pengutronix.de
Subject: [RAUC] Query regarding rauc
Date: Tue, 4 Dec 2018 16:42:14 +0530 [thread overview]
Message-ID: <CALYWmf89_tzz06wj=1GHv5tDU+ojCkn5WmyLYm5oh3BNsCuaVA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2391 bytes --]
Hi Team,
To achieve a specific requirement for us the "rauc install" command won't
work i.e due to a configuration that we have the rauc install would fail.
Though we would still like to go ahead and flashload to that partition. We
would like to know if the approach below is correct
Our understanding of rauc install suggests that it does the following
things:
1. Verify signature of the bundle
2. Run partition selection algorithm
3. Extract the tar balls from the bundle
4. Create new ext4 FS on the selected partition
5. Write appropriate tar ball to the partition
Since "rauc install" would give us errors due to our configuration we plan
to achieve this using the steps below:
1. Verify signature of the bundle (rauc info ...)
2. Partition selection algorithm (we would like to skip this)
3. Extract the tar balls from the bundle (rauc extract ..)
4. Create new ext4 FS on the selected partition + Write appropriate tar
ball to the partition (rauc write-slot ... ....)
Is the above way of bypassing the "rauc install" command for our
requirement correct? Any issues you feel might arise with this approach?
Regards,
Abhishek Rai
--
The information contained in this e-mail message (including
any
attachments) may be confidential, proprietary, privileged, or
otherwise
exempt from disclosure under applicable laws. It is intended to
be
conveyed only to the designated recipient(s). Any use, dissemination,
distribution, printing, retaining or copying of this e-mail (including
its
attachments) by unintended recipient(s) is strictly prohibited and
may
be unlawful. If you are not an intended recipient of this e-mail, or
believe
that you have received this e-mail in error, please notify the
sender
immediately (by replying to this e-mail), delete any and all
copies of
this e-mail (including any attachments) from your system, and
do not
disclose the content of this e-mail to any other person. Thank you
for your cooperation.
--
_This e-mail message (including any attachments) may be confidential,
proprietary, privileged, or otherwise exempt from disclosure under
applicable laws. If you are not an intended recipient, please delete this
message. Thank you.
_
[-- Attachment #1.2: Type: text/html, Size: 4985 bytes --]
[-- Attachment #2: Type: text/plain, Size: 65 bytes --]
_______________________________________________
RAUC mailing list
next reply other threads:[~2018-12-04 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 11:12 Abhishek Kumar Rai [this message]
2018-12-04 11:24 ` Enrico Joerns
2018-12-04 12:06 ` Abhishek Kumar Rai
2018-12-04 12:50 ` Enrico Joerns
2018-12-05 6:45 ` Abhishek Kumar Rai
2018-12-06 9:24 ` Abhishek Kumar Rai
2018-12-10 8:17 ` 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='CALYWmf89_tzz06wj=1GHv5tDU+ojCkn5WmyLYm5oh3BNsCuaVA@mail.gmail.com' \
--to=abhishekr@eximiusdesign.com \
--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