public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Christoph Pleger <Christoph.Pleger@uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFSROOT with NFS Version 3
Date: Mon, 20 Nov 2006 12:34:40 -0500	[thread overview]
Message-ID: <1164044080.5700.61.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20061120173311.154e54a6.Christoph.Pleger@uni-dortmund.de>

On Mon, 2006-11-20 at 17:33 +0100, Christoph Pleger wrote:
> Hello,
> 
> On Mon, 20 Nov 2006 08:57:16 -0500
> Joe Korty <joe.korty@ccur.com> wrote:
> 
> > On Mon, Nov 20, 2006 at 12:07:50PM +0100, Christoph Pleger wrote:
> > > Warning: Unable to open an initial console
> > 
> > This usually means /dev/console doesn't exist.  With many of
> > today's distributions, this means you didn't boot with a
> > initrd properly set up to run with your newly built kernel.
> 
> The device /dev/console exists, but init/main.c tries to open it
> read-write. As the nfsroot is mounted read-only, /dev/console cannot be
> opened read-write.

Yes. NFSv3 has an ACCESS rpc call, which allows the client to request
the correct permissions from the server rather than relying on mode
bits.
IOW: this is definitely an intentional feature.

Cheers,
  Trond


  reply	other threads:[~2006-11-20 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 15:40 NFSROOT with NFS Version 3 Christoph Pleger
2006-11-17 16:20 ` Trond Myklebust
2006-11-20 11:07   ` Christoph Pleger
2006-11-20 13:57     ` Joe Korty
2006-11-20 16:33       ` Christoph Pleger
2006-11-20 17:34         ` Trond Myklebust [this message]
2006-11-20 18:06         ` Peter Staubach
2006-11-21  0:11         ` Bill Davidsen

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=1164044080.5700.61.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=Christoph.Pleger@uni-dortmund.de \
    --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