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: linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: No /dev/root with devtmpfs?
Date: Mon, 6 Feb 2012 16:52:50 +0400	[thread overview]
Message-ID: <20120206125250.GA13217@tugrik.mns.mnsspb.ru> (raw)
In-Reply-To: <1328530227.72508.YahooMailClassic@web29004.mail.ird.yahoo.com>

On Mon, Feb 06, 2012 at 12:10:27PM +0000, Paul Parsons wrote:
> --- On Mon, 6/2/12, Kirill Smelkov <kirr@mns.spb.ru> wrote:
> > Is it somehow possible to add /dev/root to devtmpfs?
> 
> Or alternatively have /proc/mounts report the actual root device
> instead of "/dev/root" ?

Sorry, I have not included that info originally. No, it shows /dev/root
there too:

    root@(none):/# cat /proc/mounts 
    rootfs / rootfs rw 0 0
    /dev/root / ext3 ro,relatime,barrier=0,data=writeback 0 0
    devtmpfs /dev devtmpfs rw,relatime,size=61564k,nr_inodes=15391,mode=755 0 0
    tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
    proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
    sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0

  reply	other threads:[~2012-02-06 12:49 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 [this message]
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
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=20120206125250.GA13217@tugrik.mns.mnsspb.ru \
    --to=kirr@mns.spb.ru \
    --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).