From: Artem Bityutskiy <dedekind@infradead.org>
To: Philip Rakity <prakity@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Minor Error in UBIFS FAQ
Date: Wed, 10 Dec 2008 13:01:22 +0200 [thread overview]
Message-ID: <1228906882.13686.248.camel@sauron> (raw)
In-Reply-To: <69731.17422.qm@web58904.mail.re1.yahoo.com>
On Tue, 2008-12-09 at 09:07 -0800, Philip Rakity wrote:
> Could not find FAQ to generate patch. Did we mean UBIFS images (see below)
>
> How to create an UBIFS image?
> Creating UBIFS images might be a little trickier than creating JFFS2 images.
> First of all, you have to understand that UBIFS works on top of UBI which works
> on top or MTD which basically represents your raw flash. This means, that if
> you need to create an image which would be flashed to the raw flash, you should
> first create an UBIFS image, than UBI image. In other words, the process has 2
> steps.
> However, as described here,
> UBI has a volume update facility and there is an ubiupdatevol utility
> for this. So you may update UBI volumes on your running system as well.
> In this case you only need an UBIFS image, and you do not have to make the
> UBI image, i.e., the process has only 1 step in this case.
> So, there are 2 utilities:
> * mkfs.ubifs which creates UBIFS images;
> * ubinize which creates UBI images out of UBI images. <==== ERROR out of UBIFS images
The MTD web site is available here:
git://git.infradead.org/mtd-www.git
or
http://git.infradead.org/mtd-www.git
I've just fix the typo you have pointed out:
http://git.infradead.org/mtd-www.git?a=commit;h=39df2684657ab982c96d769d761cbb84e23ece80
Thank you for this notice, typo and "bad English" fixes are appreciated.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-12-10 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 17:07 Minor Error in UBIFS FAQ Philip Rakity
2008-12-10 11:01 ` Artem Bityutskiy [this message]
2008-12-10 11:18 ` 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=1228906882.13686.248.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=prakity@yahoo.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