linux-kernel - Re: No /dev/root with devtmpfs?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 8 Feb 2012 16:44:00 +0000 (GMT)
From:	Paul Parsons <lost.distance@...oo.com>
To:	Kay Sievers <kay.sievers@...y.org>,
	Kirill Smelkov <kirr@....spb.ru>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: No /dev/root with devtmpfs?

--- On Wed, 8/2/12, Kirill Smelkov <kirr@....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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/