From: Mauro Condarelli <mc5686@mclink.it>
To: rauc@pengutronix.de
Subject: [RAUC] Rauch usage hints needed
Date: Sun, 1 Dec 2019 11:55:26 +0100 [thread overview]
Message-ID: <633061c8-9eae-9232-f30b-dd430174dd4c@mclink.it> (raw)
Hi All,
I'm trying to decide if rauch is the right tool for my project.
My target is an embedded Linux with:
- SPI Flash for booting (paleolithic version of U-Boot) and possibly a
initramfs/recovery (16M total)
- A sizable SD card (8G).
Bad problem is SD is very sensitive to "unexpected" shutdowns which I
cannot prevent.
Slots should include:
- uboot (possibly never updated)
allocated in first Flash partition: /dev/mtd1
- linux kernel (rarely upgraded, if ever)
allocated in third Flash partition: /dev/mtd3
- recovery (possibly never updated)
allocated in fourth Flash partition: /dev/mtd4
probably a SquashFS, but could also be a initramfs (cpio)
copies of rauc modules could be stored in first SD partition (vfat)
/dev/mmcblk1
- system (rarely upgraded)
allocated in SD, redundant probably /dev/mmcblk0p2 and /dev/mmcblk0p3
ext4
- application (often upgraded)
allocated in SD, redundant probably /dev/mmcblk0p5 and /dev/mmcblk0p6
ext4 mounted on /home
- accumulated data (initially empty; should be preserved at all cost)
allocated in SD, not redundant, but possibly backed-up before upgrade.
ext4 mounted on /srv
At first documentation perusal I saw no direct support for MTD.
My current "solution" relies on a bunch of scripts that are rapidly growing
and a rather complex usage of OverlayFS.
I am thus looking for a "more structured" solution, possibly rauch.
Can someone advise?
I am available to give more info, if needed.
Thanks in Advance
Mauro
_______________________________________________
RAUC mailing list
next reply other threads:[~2019-12-01 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 10:55 Mauro Condarelli [this message]
2019-12-11 23:50 ` Enrico Jörns
2020-01-22 12:57 ` [RAUC] Rauc " Mauro Condarelli
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=633061c8-9eae-9232-f30b-dd430174dd4c@mclink.it \
--to=mc5686@mclink.it \
--cc=rauc@pengutronix.de \
/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