From: "Rafał Miłecki" <zajec5@gmail.com>
To: Olivier Valentin <valentio@free.fr>,
openwrt-devel@lists.openwrt.org,
MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: Identifying UBI volume instance / storing UBI volume metadata
Date: Thu, 9 Dec 2021 23:14:38 +0100 [thread overview]
Message-ID: <85498617-e63e-c746-6f42-662b5ea3df63@gmail.com> (raw)
In-Reply-To: <48BBA9D3-3DFB-4666-9FC5-6D4431486314@free.fr>
On 9.12.2021 21:11, Olivier Valentin wrote:
> How about storing the squashfs into the rootfs ubi volume (as a bare file), start with an initramfs appended to the kernel and mount the root file with loopback block dev. The RW overlay part would be stored directly in the ubifs. (All modifications to the root image file would go in the overlay, so impossible to break the image)
>
> This way, when you flash a new firmware, everything gets wiped, and you can factory reset by rm the RW directory.
>
> It diverges quite a bit from OpenWRT usual way though.
Thanks for your reply. It doesn't fit OpenWrt's current design well but
I think it's probably time to rework OpenWrt's init if needed.
Just to make sure I understood your correctly:
Do you suggest "rootfs" UBI volume using ubifs with something like:
/root.squashfs
/overlay/
(and then initramfs as you described)?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2021-12-09 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 13:22 Identifying UBI volume instance / storing UBI volume metadata Rafał Miłecki
2021-12-09 20:17 ` valentio
[not found] ` <48BBA9D3-3DFB-4666-9FC5-6D4431486314@free.fr>
2021-12-09 22:14 ` Rafał Miłecki [this message]
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=85498617-e63e-c746-6f42-662b5ea3df63@gmail.com \
--to=zajec5@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=valentio@free.fr \
/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