[oe] RFC: stop mounting /dev/mtdblockX but mount mtdX (without /dev) instead

[Hans Henry von Tresckow]

sounds OK to me. Will this improve performance as well?

On 2/21/07, Koen Kooi <koen at dominion.kabel.utwente.nl> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Chris Ball from the OLPC project was kind (and patient) enough to explain
> the first item
> of http://www.linux-mtd.infradead.org/archive/tech/faq.html to me.
>
> It seems that most machines in OE with MTD have something like:
>
> /dev/mtdblock2  /               jffs2   defaults        1  1
> /dev/mtdblock3  /home           jffs2   defaults        1  1
>
> in their fstab, which apparently is wrong. The trick to understanding the
> FAQ entry is not
> to think in terms of actual devices and controllers, but in terms of
> fstab. So 'block
> devices' translate to the emulated block devices present as /dev/mtdblockX
> and 'mtd'
> refers to mtdX.
>
> The correct fstab should be:
>
> mtd2  /         jffs2   defaults        1  1
> mtd3  /home     jffs2   defaults        1  1
>
> I don't know which kernel version introduced it, but it seems to work on
> 2.6.16.
>
> What do you think?
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFF3Kl6MkyGM64RGpERAhiaAKCdBvq8lwBfM2lzzt+vGS28KcY1VwCeNgvN
> Fyi+w99uUA+KF2bZOdDLBq0=
> =bELj
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>