From: Uladzimir Bely <ubely@ilbers.de>
To: vt <venu.thachappilly@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Questions upgrade mechanism and read-only file system
Date: Wed, 21 Sep 2022 09:33:36 +0300 [thread overview]
Message-ID: <25602913.1r3eYUQgxm@home> (raw)
In-Reply-To: <eb20bdaa-503e-41e3-aaaa-06c22ec1507an@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3991 bytes --]
next prev parent reply other threads:[~2022-09-21 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 18:31 vt
2022-09-21 6:33 ` Uladzimir Bely [this message]
2022-09-22 9:37 ` vt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=25602913.1r3eYUQgxm@home \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=venu.thachappilly@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox