From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"umar@janteq.com" <umar@janteq.com>
Subject: Re: Discovering current MTD partition
Date: Thu, 28 Apr 2011 10:37:37 +0300 [thread overview]
Message-ID: <1303976257.2778.86.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.1104280929290.15966@lnxricardw.se.axis.com>
On Thu, 2011-04-28 at 09:31 +0200, Ricard Wanderlof wrote:
> On Wed, 27 Apr 2011, umar@janteq.com wrote:
>
> > Hi,
> >
> > /proc/mounts as well doesn't relay any info about /dev/mtdXX.
>
> Sorry, you are right of course. It just seems to say /dev/root on my
> system.
>
> The df command however seems to figure out which mtd device is mounted on
> / . I don't know exactly how it finds this out though. I'm pretty sure it
> uses /proc/mounts, because if /proc/mounts is missing it doesn't output
> anything, but it must be getting extra information from somewhere.
>
> /Ricard
Well, the best it to look at df sources. But here is my guess:
/dev/root must have come from the kernel command line, if I'm not
mistaken. You can find out what is your /dev/root from /proc/cmdline -
find rootfs=<xxx> there, and xxx is your device.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-28 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 23:43 Discovering current MTD partition Umar Qureshey
2011-04-27 5:31 ` Artem Bityutskiy
2011-04-27 6:22 ` Ricard Wanderlof
2011-04-27 17:08 ` umar
2011-04-28 7:31 ` Ricard Wanderlof
2011-04-28 7:37 ` Artem Bityutskiy [this message]
2011-04-28 8:00 ` Ricard Wanderlof
2011-04-28 8:52 ` Artem Bityutskiy
2011-04-28 9:09 ` Ricard Wanderlof
2011-04-27 7:25 ` umar
[not found] ` <4DB7C9F9.9000609@free-electrons.com>
2011-04-27 17:14 ` umar
2011-04-28 4:27 ` Iwo Mergler
2011-04-28 7:39 ` Ricard Wanderlof
2011-04-28 17:26 ` umar
2011-04-28 17:48 ` Artem Bityutskiy
2011-04-29 0:53 ` umar
2011-04-28 18:08 ` Bjørn Forsman
2011-04-28 18:21 ` Atlant Schmidt
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=1303976257.2778.86.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
--cc=umar@janteq.com \
/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