From: "Mark Gollahon" <golly@stellarwerx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: stop mounting /dev/mtdblockX but mount mtdX (without/dev) instead
Date: Thu, 22 Feb 2007 13:20:51 -0500 (EST) [thread overview]
Message-ID: <1172168450.8014@gatekeeper.stellarwerx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
So how does this change the "root=" kernel command line
parameter? Would it now be "root=mtdX"?
Regards,
-Mark Gollahon
Koen Kooi 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
reply other threads:[~2007-02-22 18:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1172168450.8014@gatekeeper.stellarwerx.com \
--to=golly@stellarwerx.com \
--cc=openembedded-devel@lists.openembedded.org \
/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