All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Paul Parsons <lost.distance@yahoo.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Kirill Smelkov <kirr@mns.spb.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: No /dev/root with devtmpfs?
Date: Wed, 08 Feb 2012 09:20:14 -0800	[thread overview]
Message-ID: <4F32AECE.4010308@zytor.com> (raw)
In-Reply-To: <1328719440.33661.YahooMailClassic@web29013.mail.ird.yahoo.com>

On 02/08/2012 08:44 AM, Paul Parsons wrote:
> 
> Could you simply use /etc/fstab to identify the root partition?
> 

That's not a very good thing, as it is much more likely to be wrong.

It would be a good thing to have the /dev/root symlink *IF* a valid root
device exists (defined as a device node appearing which has the same
device number as reported by stat on the root directory), if nothing
else because we have had one available for a very long time and this is
needless breakage.

Obviously, if such a device doesn't exist (btrfs, NFS, tmpfs) then don't.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-02-08 17:20 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 [this message]
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=4F32AECE.4010308@zytor.com \
    --to=hpa@zytor.com \
    --cc=kay.sievers@vrfy.org \
    --cc=kirr@mns.spb.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.