From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 7145531540303249408
Date: Tue, 20 Sep 2022 11:31:46 -0700 (PDT)
From: vt <venu.thachappilly@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Message-Id: <eb20bdaa-503e-41e3-aaaa-06c22ec1507an@googlegroups.com>
Subject: Questions upgrade mechanism and read-only file system
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_12448_45931309.1663698706196"
X-TUID: AFvhpU4qjvon

------=_Part_12448_45931309.1663698706196
Content-Type: multipart/alternative; 
	boundary="----=_Part_12449_567395684.1663698706196"

------=_Part_12449_567395684.1663698706196
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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

------=_Part_12449_567395684.1663698706196
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

I am new to Isar (and embedded software development too). I have gone throu=
gh 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 appro=
ach and the build performance.<div><br></div><div>I am trying to figure out=
 if it would fit our requirements which at a high level are:<div><br></div>=
<div>1. Debian based OS for our intel based appliances.</div><div>2. Prefer=
ably read-only file system to prevent accidental installation of software a=
nd modifications. Configuration is modifiable and hence would need to be re=
ad-write.&nbsp;</div><div>3. Preferably atomic image based upgrades so that=
 we can keep OS+app+dependencies in sync. A failed upgrade should go back t=
o the last working version.</div><div><br></div><div>What is the recommende=
d upgrade mechanism for Isar? Are image based upgrades possible? Where can =
I find samples or documentation regarding this.</div><div><br></div><div>Is=
 read-only file system an option? Any pointers?</div><div><br></div><div>Th=
anks in advance.</div><div>- venu</div></div>
------=_Part_12449_567395684.1663698706196--

------=_Part_12448_45931309.1663698706196--