From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7145531540303249408 X-Received: by 2002:a05:6512:401c:b0:49f:4b2e:7153 with SMTP id br28-20020a056512401c00b0049f4b2e7153mr8972564lfb.443.1663742025439; Tue, 20 Sep 2022 23:33:45 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:ac2:5e7b:0:b0:48b:2227:7787 with SMTP id a27-20020ac25e7b000000b0048b22277787ls224187lfr.3.-pod-prod-gmail; Tue, 20 Sep 2022 23:33:43 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4j9y6dN9mWjFlStgoHuMG/NqDLEWolB6JCZdWuHwxQVC8w7F7rGOsn0AF5HWUFnrsSQLLB X-Received: by 2002:a05:6512:2308:b0:497:a290:cef6 with SMTP id o8-20020a056512230800b00497a290cef6mr10051944lfu.488.1663742023738; Tue, 20 Sep 2022 23:33:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663742023; cv=none; d=google.com; s=arc-20160816; b=lR5svSHEUeSamZFRBiRiLJO12ptTIyeUesRizC4qB9uMcNiLGduipr7riur/s1KPOX +xCi5hGFEAKciy47/xpvmmkGDuof1dboBu+oZv0kLPRc3uQwt1wzu6qGqF4+HZWMmFpq EDdVm1tFhbLIimXCe07X5tsB6FDGVzko1UzGriTjllA5L7waPGmPYeGgCyRXU4Tfdp9G ryI9XsOnZHTfXeQxLFm9wTgr23WWy6PIQ5SQL8pRQbb93Djyk4axfb2tHaiF12MFf/A7 2VLicsvh9Yd1GthHSCXyZPpOlGLnrziflUmuNePSApNWzR4QMqFsjyf9zCm7sBm37k8Q A+EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=1BVwoHmLDTQowA46yFn6SCjrUgTfn2PNr09Rq+Ovgqo=; b=drmcUib2gWgKV+cqNzLfGlrNfrHf6s+YaXCv0y8Rmf3vI4YipSChmqGaksmdFZHUr2 Xdml56fEj855g5XBDZofxtOQaaaWs8//88xAcbCr7wykWm7w+X4HUoZzk5dFf+/xIaFu bWD0gV7L1Sa5yMaaEH569r8olsXb4uFjoUNXedPLr0/G+rp1u/sryVOsoXjIfDF/DI+e OVhoyBOyq8N8JXHDTpaKhA5cbulNAL9BXIBgJ67lgLkO88a47kJj3ntHPM6lL+AUdHXD Qj7714HLlbKhu2yb7fEwhYw6yjuxMfnMLxKOZdSpE1ZxEapxrZrONVntNmFRlVBQDJqI tBRQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id v18-20020a2ea612000000b0026c427c1599si86192ljp.1.2022.09.20.23.33.43 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 20 Sep 2022 23:33:43 -0700 (PDT) Received-SPF: pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ubely@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=ubely@ilbers.de Received: from home.localnet (44-208-124-178-static.mgts.by [178.124.208.44] (may be forged)) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 28L6Xe6L025404 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 21 Sep 2022 08:33:41 +0200 From: Uladzimir Bely To: vt Cc: isar-users Subject: Re: Questions upgrade mechanism and read-only file system Date: Wed, 21 Sep 2022 09:33:36 +0300 Message-ID: <25602913.1r3eYUQgxm@home> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="nextPart2193139.vFx2qVVIhK" Content-Transfer-Encoding: 7Bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: KocXoHQOK+yI This is a multi-part message in MIME format. --nextPart2193139.vFx2qVVIhK Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" In the email from Tuesday, 20 September 2022 21:31:46 +03 user vt wrote: > I am new to Isar (and embedded software development too). I have gone > through the documentation and have had some success running through the > samples, generating images and booting them in qemu and vmware. I still > have to dig deeper into how it all works, but overall I like the > layered/modular approach and the build performance. > > I am trying to figure out if it would fit our requirements which at a high > level are: > > 1. Debian based OS for our intel based appliances. > 2. Preferably read-only file system to prevent accidental installation of > software and modifications. Configuration is modifiable and hence would > need to be read-write. > 3. Preferably atomic image based upgrades so that we can keep > OS+app+dependencies in sync. A failed upgrade should go back to the last > working version. > > What is the recommended upgrade mechanism for Isar? Are image based > upgrades possible? Where can I find samples or documentation regarding this. > > Is read-only file system an option? Any pointers? > > Thanks in advance. > - venu Hello. You might want to look at swupdate that is implemented in 'isar-cip-core' layer on top of Isar: https://gitlab.com/cip-project/cip-core/isar-cip-core[1] It does what you've requested (read-only rootfs, image-based upgrade) and provides some documentation. -- Uladzimir Bely -------- [1] https://gitlab.com/cip-project/cip-core/isar-cip-core --nextPart2193139.vFx2qVVIhK Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

In the email from Tuesday, 20 September 2022 21:31:46 +03 user vt wrote:

> I am new to Isar (and embedded software development too). I have gone

> through the documentation and have had some success running through the

> samples, generating images and booting them in qemu and vmware. I still

> have to dig deeper into how it all works, but overall I like the

> layered/modular approach and the build performance.

>

> I am trying to figure out if it would fit our requirements which at a high

> level are:

>

> 1. Debian based OS for our intel based appliances.

> 2. Preferably read-only file system to prevent accidental installation of

> software and modifications. Configuration is modifiable and hence would

> need to be read-write.

> 3. Preferably atomic image based upgrades so that we can keep

> OS+app+dependencies in sync. A failed upgrade should go back to the last

> working version.

>

> What is the recommended upgrade mechanism for Isar? Are image based

> upgrades possible? Where can I find samples or documentation regarding this.

>

> Is read-only file system an option? Any pointers?

>

> Thanks in advance.

> - venu


Hello.


You might want to look at swupdate that is implemented in 'isar-cip-core' layer on top of Isar:

https://gitlab.com/cip-project/cip-core/isar-cip-core


It does what you've requested (read-only rootfs, image-based upgrade) and provides some documentation.


--

Uladzimir Bely


--nextPart2193139.vFx2qVVIhK--