From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: References: From: Enrico Joerns Message-ID: Date: Thu, 11 Jul 2019 10:23:17 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Subject: Re: [RAUC] Question about mounting application FS List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="windows-1252"; Format="flowed" Errors-To: rauc-bounces@pengutronix.de Sender: "RAUC" To: Patrick Schneider Cc: "rauc@pengutronix.de" Hi Patrick, On 7/11/19 9:42 AM, Patrick Schneider wrote: > Hi there, > = > we are currently using RAUC in A + B mode with rootFS and appFS in each s= lot. 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= =92t find = > a hint how to do that properly in the RAUC documentation. this can be done using proper udev rules for creating device aliases (symli= nks) = that are then used for mounting. How this is to be solved in detail depends a little on which storage type y= ou = are actually using and how you boot. Maybe you can add some more details here. We have a work-in-progress Pull-Request targeting a documentation update fo= r = this. It actually handles data partition mounting but the considerations ar= e = valid for an appfs, too. https://github.com/rauc/rauc/pull/370 Best regards, Enrico P.S: I've moderated your mail free, but please consider subscribing to the = mailing list to ease sending / receiving messages to / from this list. -- = Pengutronix e.K. | Enrico J=F6rns | 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