public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: util-linux@vger.kernel.org
Subject: Re: new mount is broken w/regard to devnames in /etc/fstab
Date: 20 May 2013 10:03:00 +0200	[thread overview]
Message-ID: <CXE+rHTuCXB@helmut.hullen.de> (raw)
In-Reply-To: <5198086A.1010903@tlinx.org>

Hallo, Linda,

Du meintest am 18.05.13:



> There are 2 problems -- they are unlikely to be
> directly related, but are in so much as they are in the new version
> of mount.

> 1) How is one supposed to get the real root device?
> It's not /dev/root -- and on my system /dev/root doesn't even exist.
> (though to be fair, it has in the past -- udev musta got sloppy this
> time, and did point to the real root device).  But how can I get
> /proc to display the real root device instead of some fake name.

        rdev

should do the job.

Viele Gruesse!
Helmut

  parent reply	other threads:[~2013-05-20  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-18 23:02 new mount is broken w/regard to devnames in /etc/fstab Linda Walsh
2013-05-20  7:53 ` Karel Zak
2013-05-20  8:03 ` Helmut Hullen [this message]
2013-05-21  2:28 ` Helmut Hullen

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=CXE+rHTuCXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --cc=util-linux@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