From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>,
Atlant Schmidt <aschmidt@dekaresearch.com>
Subject: RE: UBI partitioning in embedded device?
Date: Mon, 18 Apr 2011 16:35:26 +0300 [thread overview]
Message-ID: <1303133726.8589.8.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1104181531260.30071@lnxricardw.se.axis.com>
On Mon, 2011-04-18 at 15:33 +0200, Ricard Wanderlof wrote:
> I think what I'm most worried about is some bug in UBI causing the
> critical data to be lost at some point. And as you said, some form of
> backup would definitely help.
Well, good testing and redundancy would be the answer...
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-18 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 6:44 UBI partitioning in embedded device? Ricard Wanderlof
2011-04-18 7:09 ` Artem Bityutskiy
2011-04-18 11:45 ` Atlant Schmidt
2011-04-18 12:53 ` Ricard Wanderlof
2011-04-18 13:01 ` Artem Bityutskiy
2011-04-18 13:33 ` Ricard Wanderlof
2011-04-18 13:35 ` Artem Bityutskiy [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=1303133726.8589.8.camel@localhost \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.