From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Wed, 02 Jul 2025 09:28:34 +0200 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uWrtS-00DE7P-2a for lore@lore.pengutronix.de; Wed, 02 Jul 2025 09:28:34 +0200 Received: from localhost ([127.0.0.1] helo=metis.whiteo.stw.pengutronix.de) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1uWrtS-0008Kk-E6; Wed, 02 Jul 2025 09:28:34 +0200 Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[IPv6:::1]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1uWrtJ-0008Gh-RX; Wed, 02 Jul 2025 09:28:25 +0200 Message-ID: <6f35f8dd0d528d2addf4f46d4ba702f3b73a00de.camel@pengutronix.de> To: =?UTF-8?Q?=E5=A4=A7=E5=8E=9F_=E5=8C=A0=E6=B1=B0?= , "rauc@pengutronix.de" Date: Wed, 02 Jul 2025 09:28:24 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4-2 MIME-Version: 1.0 Subject: Re: [RAUC] Question about updating using Casync in RAUC v1.8 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: , From: =?utf-8?q?Enrico_J=C3=B6rns_via_RAUC?= Reply-To: Enrico =?ISO-8859-1?Q?J=F6rns?= 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.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false Hi Ohara, Am Mittwoch, dem 02.07.2025 um 02:28 +0000 schrieb =E5=A4=A7=E5=8E=9F =E5= =8C=A0=E6=B1=B0 via RAUC: > Hi, > I have a question about updating using Casync in RAUC v1.8. Note that this version of RAUC is already 3 years old and should probably n= ot be used for new developments. > 1. The documentation says that when updating using Casync, > the current SLOT in the boot is used as the seed and the differences are = downloaded. > https://rauc.readthedocs.io/en/v1.8/advanced.html#rauc-casync-support=C2= =A0 > If this is the case, will rewriting the current SLOT during the update ca= use problems? What's the use case for rewriting the current slot? In most cases, this should be the slot the system is currently booted from. > 2.If so, is it necessary to set the SLOT to ReadOnly? The casync seed store is internally realized using symlinks with storage lo= cations encoded. After seeding, when actually reading a chunk from the store, this should be= hashed and compared again and produce an error internally if the underlying data changed. This = should lead to ignoring this seed chunk and to download the chunk from the (remote) chunk store ins= tead. So, yes, in general the seed slot should be read-only. But it should also work if some of the data gets corrupted between seeding = and writing. Further details on this are probably more a casync-related question. Regards, Enrico > 3.If not, or if it is not necessary to set ReadOnly, please tell us why. >=20 > That is all. >=20 > Regards, > =E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82=E2=80=82Ohara > -------------------------------- > OSAKA NDS Co.,Ltd. > Ohara Shota > e-mail: shota.ohara@nds-osk.co.jp > -------------------------------- >=20 --=20 Pengutronix e.K.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| Enrico J=C3=B6rns=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| Embedded Linux Consulting & Support=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0| https://www.pengutronix.de/ | Steuerwalder Str. 21=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0| Phone: +49-5121-206917-180=C2=A0=C2=A0| 31137 Hildesheim, Germany=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0| Fax:=C2=A0=C2= =A0=C2=A0+49-5121-206917-9=C2=A0=C2=A0=C2=A0=C2=A0|