From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 28 Feb 2022 09:55:08 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nOboC-00D3fK-9T for lore@lore.pengutronix.de; Mon, 28 Feb 2022 09:55:08 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nOboB-0000M2-IN; Mon, 28 Feb 2022 09:55:07 +0100 Received: from mail.kmu-office.ch ([2a02:418:6a02::a2]) by metis.ext.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nObnu-0000Lt-6l for rauc@pengutronix.de; Mon, 28 Feb 2022 09:54:50 +0100 Received: from webmail.kmu-office.ch (unknown [IPv6:2a02:418:6a02::a3]) by mail.kmu-office.ch (Postfix) with ESMTPSA id 9E62B5C0D0D for ; Mon, 28 Feb 2022 09:54:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=agner.ch; s=dkim; t=1646038489; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=Yg3LkVMIlLAIlirR4pxzUVp3iGolCPCAQxNy7DWsQ30=; b=Qh849Ak8nLHgR8lArEddwDkxtBJSOAgd4xqq+spUIgPi6nYe9befbQb01NYN0aextidO8N mPLAdcwWZjzPt7aS0saGo3tUjHNfvG7tdGffN3B1COxdv+JAT+y3BUAHyoGgU+52RSRfhs tCRlT4aW80KpeJfJKN/zXno+Xr21y28= MIME-Version: 1.0 Date: Mon, 28 Feb 2022 09:54:49 +0100 From: Stefan Agner To: rauc@pengutronix.de User-Agent: Roundcube Webmail/1.4.9 Message-ID: <0ca1f5b159c309fced97a4ff34b371db@agner.ch> X-Sender: stefan@agner.ch X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-3.2 required=4.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.2 Subject: [RAUC] Bootloader change X-BeenThere: rauc@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "RAUC" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: rauc-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false Hi List, We are using rauc since several releases successfully in Home Assistant OS. Thanks for this awesome piece of open source software! With the upcoming release we plan to switch from Barebox to GRUB2 for x86-64 platform. The main reason being GRUB2 also supporting aarch64, and is generally more common in x86-64 world. This requires a change to system.conf obviously. However, only with the new upgrade the necessary tools and new system.conf are shipped. From what I can tell there is no built-in mechanism for such a change in rauc. Is there a best practice for such a change? We use a A/B layout with a single boot loader. My current implementation ships with two GRUB2 environment defaulting ORDER to "A B" and "B A" respectively. I then use a hook to copy the right environment based on RAUC_SLOT_BOOTNAME. With that the correct boot slot get booted on upgrade. However, downgrading won't work as the upgraded rauc uses a system.conf for grub now. Instead of using the hook to handle the environment "manually", it would be nice to have rauc handle it for the (other) boot loader present in the update bundle. For that to work the update bundle would need some mechanism to override system.conf. Of course this would need tooling to be present for both boot loaders. Thoughts? -- Stefan _______________________________________________ RAUC mailing list