From: Enrico Joerns <ejo@pengutronix.de>
To: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Regarding usage of hook
Date: Wed, 26 Sep 2018 16:22:35 +0200 [thread overview]
Message-ID: <4995aef7-7e3c-835c-8bce-a1e1c94a18ab@pengutronix.de> (raw)
In-Reply-To: <CALYWmf9Y1_OK-fttacSJ9eo8xP0xsa2gbLg9B8m+aw56Yc+3SA@mail.gmail.com>
Hi Abhishek,
On 9/26/18 1:59 PM, Abhishek Kumar Rai wrote:
>
> Abhishek Kumar Rai <abhishekr@eximiusdesign.com <mailto:abhishekr@eximiusdesign.com>>
>
> 5:12 PM (16 minutes ago)
> to rauc-request
>
> Hi team ,
>
> I am new to rauc .Please solve my query
>
> I have written system.conf file
>
> {{{
> abhishek@abhishek-Latitude-5490:~$ cat system.conf
> [system]
> compatible=eximius
> bootloader=uboot
> mountprefix=/mnt/rauc
> statusfile=/factory/rauc.status
>
> [keyring]
> path=cert.pem
>
> [...]
>
> [slot.appdata.0]
> #device=/dev/mmcblk1p8
> device=/dev/disk/by-path/platform-219c000.usdhc-part8
> type=ext4
> parent=rootfs.0
>
> [slot.appdata.1]
> #device=/dev/mmcblk1p9
> device=/dev/disk/by-path/platform-219c000.usdhc-part9
> type=ext4
> parent=rootfs.1
> }}}
>
> how to use hook in order to preserve the data of appdata0, while installing bundle .
> In which file i have to give hook option?
Hooks are part of the bundle, thus you have to define them in the bundle's manifest, e.g.:
[hooks]
filename=yourhookscript.sh
[image.appdata]
image=foo.img
hooks=install
Note that your bundle generation has to place yourhookscript.sh into the bundle in order to make this work.
Potentially, you could also do this in a post-install hook for your appfs in case you know where your appdata copies are located.
Best regards,
Enrico
> 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.
Not sure if I will get in prison when replying on this mail on a world-accessible mailing list... ;)
--
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
next prev parent reply other threads:[~2018-09-26 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 11:59 Abhishek Kumar Rai
2018-09-26 14:22 ` Enrico Joerns [this message]
2018-09-26 15:30 ` Abhishek Kumar Rai
2018-09-27 6:46 ` 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=4995aef7-7e3c-835c-8bce-a1e1c94a18ab@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=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