From: Patrick Schneider <patrick.schneider@bhtronik.de>
To: "rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: [RAUC] Question about mounting application FS
Date: Thu, 11 Jul 2019 07:42:46 +0000 [thread overview]
Message-ID: <AM0PR08MB3842F254E74D986A4C9F206CEBF30@AM0PR08MB3842.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 505 bytes --]
Hi there,
we are currently using RAUC in A + B mode with rootFS and appFS in each slot. So far so good, integration worked and RAUC does its job in updating all the slots and communicating with barebox. Now we wondered what is best practice in mounting the right appFS for the corresponding rootFS? When rootFS0 boots the appFS0 has to be mounted and when rootFS1 boots we need appFS1. We couldn't find a hint how to do that properly in the RAUC documentation.
Any help appreciated!
Regards,
Patrick
[-- Attachment #1.2: Type: text/html, Size: 2386 bytes --]
[-- Attachment #2: Type: text/plain, Size: 66 bytes --]
_______________________________________________
RAUC mailing list
next reply other threads:[~2019-07-11 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 7:42 Patrick Schneider [this message]
2019-07-11 8:23 ` 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=AM0PR08MB3842F254E74D986A4C9F206CEBF30@AM0PR08MB3842.eurprd08.prod.outlook.com \
--to=patrick.schneider@bhtronik.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