All of lore.kernel.org
 help / color / mirror / Atom feed
* RFC: stop mounting /dev/mtdblockX but mount mtdX (without /dev) instead
@ 2007-02-21 20:20 Koen Kooi
  2007-02-21 22:01 ` Hans Henry von Tresckow
  0 siblings, 1 reply; 2+ messages in thread
From: Koen Kooi @ 2007-02-21 20:20 UTC (permalink / raw)
  To: Using the OpenEmbedded metadata to build Linux Distributions

-----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-----



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFC: stop mounting /dev/mtdblockX but mount mtdX (without /dev) instead
  2007-02-21 20:20 RFC: stop mounting /dev/mtdblockX but mount mtdX (without /dev) instead Koen Kooi
@ 2007-02-21 22:01 ` Hans Henry von Tresckow
  0 siblings, 0 replies; 2+ messages in thread
From: Hans Henry von Tresckow @ 2007-02-21 22:01 UTC (permalink / raw)
  To: openembedded-devel

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

On 2/21/07, Koen Kooi <koen@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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-02-21 22:02 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-21 20:20 RFC: stop mounting /dev/mtdblockX but mount mtdX (without /dev) instead Koen Kooi
2007-02-21 22:01 ` Hans Henry von Tresckow

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.