From: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
To: ejo@pengutronix.de
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Regarding usage of hook
Date: Wed, 26 Sep 2018 21:00:55 +0530 [thread overview]
Message-ID: <CALYWmf_E2N9bebWaUSrK3iK+7wUwO0jQhhTsy45NNh_h0_7kTg@mail.gmail.com> (raw)
In-Reply-To: <4995aef7-7e3c-835c-8bce-a1e1c94a18ab@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 4408 bytes --]
Hi Enrico,
Thanks for your prompt reply.
In my design , I have to do following things.
- Create a RAUC bundle consisting of App images and dbs ->
ProductControl.bin, Controls.bin, Operations.bin, ProductControl.db,
Controls.db, Operations.db etc. ->*Bundle.raucb*
*- *- On installation, both the images and db should go into AppFS.
DataFS should remain unaffected.
- “Post Install Hook” in RAUC shall be used to copy configuration
data from the current slot of DataFS to the newly installed slot.
*Can we achieve above scenario(with system.conf in previous mail)
**using * “Post
Install Hook” in manifest file. ?
*Regards,*
*Abhishek*
On Wed, Sep 26, 2018 at 7:52 PM Enrico Joerns <ejo@pengutronix.de> wrote:
> 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 |
>
>
--
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: 7779 bytes --]
[-- Attachment #2: Type: text/plain, Size: 65 bytes --]
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2018-09-26 15:31 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
2018-09-26 15:30 ` Abhishek Kumar Rai [this message]
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=CALYWmf_E2N9bebWaUSrK3iK+7wUwO0jQhhTsy45NNh_h0_7kTg@mail.gmail.com \
--to=abhishekr@eximiusdesign.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