linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kirill Smelkov <kirr@mns.spb.ru>
To: Paul Parsons <lost.distance@yahoo.com>
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: Mon, 13 Feb 2012 12:25:39 +0400	[thread overview]
Message-ID: <20120213082539.GA5930@tugrik.mns.mnsspb.ru> (raw)
In-Reply-To: <1328879437.80871.YahooMailClassic@web29006.mail.ird.yahoo.com>

On Fri, Feb 10, 2012 at 01:10:37PM +0000, Paul Parsons wrote:
> --- 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

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.


Thanks,
Kirill

  reply	other threads:[~2012-02-13  8:22 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
2012-02-13  8:25               ` Kirill Smelkov [this message]
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=20120213082539.GA5930@tugrik.mns.mnsspb.ru \
    --to=kirr@mns.spb.ru \
    --cc=hpa@zytor.com \
    --cc=kay.sievers@vrfy.org \
    --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;
as well as URLs for NNTP newsgroup(s).