Re: UBI: about ubinize tool

[Artem Bityutskiy <dedekind@infradead.org>]

On Wed, 2008-03-26 at 12:02 +0800, Nancy wrote:
> Hi,
>     As I know, ubinize can generate UBI images. I don't understand why
> its .cfg file need parameter "image=ubifs.img", why can't it collect
> the content
> from the defined vol_id automatically and output to file "ubi.img"?

You may want to create an UBI image with 3 UBI volumes. In this case you
may want to specify 3 different images as the contents of the UBI
volumes.

For example, you may want to have "/home" UBIFS volume, "/" UBIFS
volume, and "/boot" JFFS2 volume. In this case you prepare
"home.ubifs.img", "rootfs.ubifs.img" with mkfs.ubifs, and
"boot.jffs2.img" with mkfs.jffs2. Then you create a config file where
you ask ubinize to create an UBI image, add 3 volumes to it, the first
volume should have ID 5 (you specify vol_id=5), the second volume should
have ID 10, and the third volume ID 0, and so on.

This is the idea.

>     How to make the input image file? mkfs.ubifs can only generate
> ubifs image. If it was another filesystem eg. vfat, there's no tool.

ubinize does not care about the contents of the image you ask it to put
to the volume. It may be anything. I do not know how one can prepare
vfat image, there should be a tool or a way to do this.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)