From: Paul Parsons <lost.distance@yahoo.com>
To: Kay Sievers <kay.sievers@vrfy.org>, Kirill Smelkov <kirr@mns.spb.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: No /dev/root with devtmpfs?
Date: Wed, 8 Feb 2012 16:44:00 +0000 (GMT) [thread overview]
Message-ID: <1328719440.33661.YahooMailClassic@web29013.mail.ird.yahoo.com> (raw)
In-Reply-To: <20120208073559.GA3163@tugrik.mns.mnsspb.ru>
--- On Wed, 8/2/12, Kirill Smelkov <kirr@mns.spb.ru> wrote:
> "On what disk/partition was / mounted?" is a well-defined
> question for
> cases when backing store is local hdd, so there should be
> well-defined
> answer.
>
> Previously it was /dev/root, but if /dev/root is not good
> there should be
> some other way for getting the answer. With ext2 I've
> switched to
> `mountpoint -d /` and then grepping major/minor in
> /proc/partitions, but
> with major=0 case I suspect this won't work.
>
>
> My use case is to check md5 sum of mbr + bootloader area +
> root-partition early right after the boot, to verify whether
> software is
> not corrupt, and for doing so it was useful to know / ->
> root-partition
> -> whole block device. It's not tivo, just checking for
> medium damage. (I
> understand this would be better done in the early bootloader
> but that
> part is out of my control)
Could you simply use /etc/fstab to identify the root partition?
next prev parent reply other threads:[~2012-02-08 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 11:18 No /dev/root with devtmpfs? Kirill Smelkov
2012-02-06 12:10 ` Paul Parsons
2012-02-06 12:52 ` Kirill Smelkov
2012-02-06 19:45 ` Kay Sievers
2012-02-07 7:55 ` Kirill Smelkov
2012-02-07 10:05 ` Kay Sievers
2012-02-08 7:35 ` Kirill Smelkov
2012-02-08 16:44 ` Paul Parsons [this message]
2012-02-08 17:20 ` H. Peter Anvin
2012-02-08 17:25 ` Kay Sievers
2012-02-08 17:36 ` H. Peter Anvin
2012-02-10 9:04 ` Kirill Smelkov
2012-02-10 13:10 ` Paul Parsons
2012-02-13 8:25 ` Kirill Smelkov
2012-02-13 18:48 ` H. Peter Anvin
2012-02-13 19:30 ` Kay Sievers
2012-02-13 19:32 ` H. Peter Anvin
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=1328719440.33661.YahooMailClassic@web29013.mail.ird.yahoo.com \
--to=lost.distance@yahoo.com \
--cc=kay.sievers@vrfy.org \
--cc=kirr@mns.spb.ru \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).