From: "H. Peter Anvin" <hpa@zytor.com>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: Paul Parsons <lost.distance@yahoo.com>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org
Subject: Re: No /dev/root with devtmpfs?
Date: Mon, 13 Feb 2012 10:48:30 -0800 [thread overview]
Message-ID: <4F395AFE.9010802@zytor.com> (raw)
In-Reply-To: <20120213082539.GA5930@tugrik.mns.mnsspb.ru>
On 02/13/2012 12:25 AM, Kirill Smelkov wrote:
>>
>> The bootloader might pass the root partition to the kernel via the
>> "root=" kernel parameter; these can be read at /proc/cmdline.
>> For example, on an HP iPAQ hx4700: root=/dev/mtdblock2
>
> This does not work universally either, for example for
>
> root=PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF
>
>
> the kernel scans partitions and finds one for root by partition uuid
> (see name_to_dev_t() in init/do_mounts.c).
>
> That's exactly my situation - I have universal flash image which can
> bee booted via CF slot (on several boards, thus will have different
> /dev/hd? or /dev/sd?) and via usb/cardreader (again different /dev/
> entry), and root is mounted by partition id.
>
> The kernel has no problem finding root partition and mounting it. I just
> needed a sane and robust way to know its choice.
>
In this case it's not the kernel, but the initramfs which does this
lookup. In that case the initramfs could/should create /dev/root.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-02-13 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 11:18 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
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 [this message]
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=4F395AFE.9010802@zytor.com \
--to=hpa@zytor.com \
--cc=kay.sievers@vrfy.org \
--cc=kirr@mns.spb.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lost.distance@yahoo.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
Powered by JetHome