From: Paul Parsons <lost.distance@yahoo.com>
To: Kirill Smelkov <kirr@mns.spb.ru>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org
Subject: Re: No /dev/root with devtmpfs?
Date: Fri, 10 Feb 2012 13:10:37 +0000 (GMT) [thread overview]
Message-ID: <1328879437.80871.YahooMailClassic@web29006.mail.ird.yahoo.com> (raw)
In-Reply-To: <20120210090425.GA3997@tugrik.mns.mnsspb.ru>
--- On Fri, 10/2/12, Kirill Smelkov <kirr@mns.spb.ru> wrote:
> > Could you simply use /etc/fstab to identify the root
> partition?
>
> Unfortunately no, because /etc/fstab can't know where the
> card will be
> inserted to boot this time - i.e. either in compactflash
> slot on
> motherboard, or through usb via cardreader. So root has to
> be determined
> at runtime.
>
> Personally I'm ok with no /dev/root symlink as long as there
> is another
> way to detect root blkdev reliably. And I'm still confised
> what's the
> rationale about why this can't be done for modern
> filesysems.
Here's another suggestion: /proc/cmdline
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
next prev parent reply other threads:[~2012-02-10 13:10 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
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 [this message]
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=1328879437.80871.YahooMailClassic@web29006.mail.ird.yahoo.com \
--to=lost.distance@yahoo.com \
--cc=hpa@zytor.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).