From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brijesh Singh <brijesh.s.singh@gmail.com>
Cc: linux-mtd@lists.infradead.org, rohitvdongre@gmail.com,
David Woodhouse <dwmw2@infradead.org>,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: Release of UBIL: ubi with log
Date: Mon, 10 May 2010 12:07:47 +0300 [thread overview]
Message-ID: <1273482467.2209.101.camel@localhost> (raw)
In-Reply-To: <h2h6b5362aa1005100203l7530e56eh1029efd4d1428b91@mail.gmail.com>
On Mon, 2010-05-10 at 14:33 +0530, Brijesh Singh wrote:
> >> insmod ubi mtd=1,ubinize.
> >> (Second parameter "ubinize" is introduced to avoid accidental loss of data.)
> >> insmod ubifs
> >> mount ubifs
> >
> > Why this ubinize parameter exists? Why you cannot detect empty media
> > just like UBI?
>
> The idea was not to accidentally ubinize mtd partition.
> For example: the file system generally don't format empty partition on
> it's own. It is forced.
File system just never formats the media, so of course they never
corrupt anything. Utilities mkfs.ext3 and the like do this instead.
In fact, you can thing of UBI the same way - it does not format, there
is ubiformat tool for that. Then, there is one single exception - empty
flash. It is just very handy to be able to attach it without ubiformat.
You can consider this as an additional usefuls feature.
And UBI does manage somehow to not corrupt anything. So the question was
- why UBIL cannot?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-05-10 9:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 12:58 Release of UBIL: ubi with log Brijesh Singh
2010-03-02 19:45 ` Artem Bityutskiy
2010-03-31 12:57 ` Corentin Chary
2010-03-31 12:59 ` Artem Bityutskiy
2010-04-01 18:54 ` Brijesh Singh
2010-04-01 11:14 ` Brijesh Singh
2010-04-01 11:59 ` Corentin Chary
2010-04-01 19:06 ` Brijesh Singh
2010-04-23 12:11 ` Artem Bityutskiy
2010-04-06 8:31 ` Artem Bityutskiy
2010-04-07 8:51 ` Brijesh Singh
2010-05-10 6:49 ` Artem Bityutskiy
2010-05-10 9:03 ` Brijesh Singh
2010-05-10 9:07 ` Artem Bityutskiy [this message]
2010-05-10 10:21 ` Brijesh Singh
2010-05-10 11:09 ` Artem Bityutskiy
2010-05-10 11:02 ` Artem Bityutskiy
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=1273482467.2209.101.camel@localhost \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=brijesh.s.singh@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rohitvdongre@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;
as well as URLs for NNTP newsgroup(s).