linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kirill Smelkov <kirr@mns.spb.ru>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: No /dev/root with devtmpfs?
Date: Tue, 7 Feb 2012 11:55:53 +0400	[thread overview]
Message-ID: <20120207075553.GB8632@tugrik.mns.mnsspb.ru> (raw)
In-Reply-To: <CAPXgP11N=8NULMH-o0Us0OuqYpP9sKe9uUKWzE35h1AiRP1Cjg@mail.gmail.com>

On Mon, Feb 06, 2012 at 08:45:24PM +0100, Kay Sievers wrote:
> On Mon, Feb 6, 2012 at 12:18, Kirill Smelkov <kirr@mns.spb.ru> wrote:
> > Recently I've reworked my system not to use udev, but use devtmpfs
> > instead and discovered there is no /dev/root symlink in devtmpfs case.
> >
> > My setup uses /dev/root early to know what is the boot device and then
> > do some operations on it like checksumming, etc...
> >
> > Now when /dev/root is gone the best workaround I could come up with is
> > to   grep /proc/partitions for '[hs]d[a-z]1'  but it's ugly and will
> > break when there are several block devices attached.
> >
> > Is it somehow possible to add /dev/root to devtmpfs?
> 
> No, devtmpfs has no business in knowing anything about the rootfs or
> who mounted what ans where. I can not create such links.
> 
> The entire concept of /dev/root is flawed anyway, and nothing should
> really depend on that.
> 
> Modern filesystems will not offer a direct relation to a single block
> device, they allocate an superblock which has a major == 0, so there
> can be by definition never such a link. Better get rid of all uses of
> /dev/root, it will just fail in the future.

Kay, thanks for explanation.

Though now I'm confused about how to know on what "place" root
filesystem was mounted... To me the question makes sense, but you say
with modern filesystems there by definition is no answer (or did I
misunderstood you?) Strange...

  reply	other threads:[~2012-02-07  7:52 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 [this message]
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=20120207075553.GB8632@tugrik.mns.mnsspb.ru \
    --to=kirr@mns.spb.ru \
    --cc=kay.sievers@vrfy.org \
    --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).