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