From: Jupiter <jupiter.hce@gmail.com>
To: Alexander Dahl <ada@thorsis.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
linux-mtd@lists.infradead.org
Subject: Re: Install Yocto image and backup
Date: Mon, 2 Nov 2020 20:16:58 +1100 [thread overview]
Message-ID: <CAA=hcWSAsKEcFaR1dCpCey_m2Z2zOxYT1N8NNjL6bNQxSrHj1A@mail.gmail.com> (raw)
In-Reply-To: <2234110.ZDGxJVC3CD@ada>
Hi Alexander,
Thanks for your advice.
> In my opinion two things are common practice:
>
> 1) Using a layer on top of raw NAND, like UBI/UBIFS nowadays, so bad blocks
> can be handled properly in a layer below your rootfs.
Yes, the UBI/UBIFS is used in NAND partitions, I guess you alluded
there is no need use the backup, right?
> 2) Using an A/B scheme for updating and using a well tested framework for
> that (instead of self written shell scripts). You don't need another NAND chip
> for that, just multiple partitions. You can still have your kernel/rootfs read-only at runtime.
If I do need to use a backup, it won't need another NAND chip, it will
be another UBI/UBIFS partition. But I would like as simple as possible
if no backup is a common practice.
Thank you very much.
Kind regards,
- jupiter
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-11-02 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 1:02 Install Yocto image and backup Jupiter
2020-11-02 8:40 ` Alexander Dahl
2020-11-02 9:16 ` Jupiter [this message]
2020-11-03 8:16 ` Alexander Dahl
2020-11-03 9:17 ` Jupiter
2020-11-03 9:48 ` [yocto] " Richard Weinberger
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='CAA=hcWSAsKEcFaR1dCpCey_m2Z2zOxYT1N8NNjL6bNQxSrHj1A@mail.gmail.com' \
--to=jupiter.hce@gmail.com \
--cc=ada@thorsis.com \
--cc=linux-mtd@lists.infradead.org \
--cc=yocto@yoctoproject.org \
/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;
as well as URLs for NNTP newsgroup(s).