Re: mkfs.jffs2 question

[David Woodhouse <dwmw2@infradead.org>]

rayl@otii.com said:
>  shouldn't number 4 also result in an 8MB image? 

Er, yes - probably. That looks like a getopt bug. I'm not sure what we 
could do differently.

>  second, if the very first dirent of the --root= argument is itself a
> dir, then it is not put into the jffs2 image.

>  i recreated my toplevel tree, ensuring that the first dirent was a
> file, not a directory.  now, all items show up just fine in the
> jffs2reader output, but the jffs2 image is the same size as it was
> before.

Presumably this is without the -p option? :)

> so maybe it's just a problem with the reader?

Mount the image on your host and verify this. I'm more inclined to believe
it's the jffs2reader at fault than mkfs.jffs2. 

	insmod mtdram total_size=8192 erase_size=64
	dd if=/dev/mtd0 of=/dev/mtd0
	mount -t jffs2 /dev/mtdblock0 /mnt/spare


--
dwmw2