mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Willy Tarreau <w@1wt.eu>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	William Estrada <MrUmunhum@popdial.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Mounting NFS root FS
Date: Sat, 02 Dec 2006 21:37:18 -0500	[thread overview]
Message-ID: <1165113438.5698.5.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20061202225528.GA27342@1wt.eu>

On Sat, 2006-12-02 at 23:55 +0100, Willy Tarreau wrote:
> I'm not saying initramfs is not powerful, and indeed your example is
> the common way of parsing cmdline for me too. What I'm saying is that
> before nfsroot stops being supported, we'll need a working replacement
> (and not "### further parse $arg"), if possible within the kernel tree
> so that people who used to build kernels to boot such machines will
> still be able to build kernels for them, even if this implies using
> an initramfs with some tools in it.
> 
> The real danger of removing support for in-kernel features like this
> is to leave people with no solution at all (because they don't know
> how to proceed), and their workarounds are often worse than the
> problem that we tried to fix in the first place.

It hasn't been removed yet. However most distributions choose not to
enable it because that would force them to compile the NFS client into
the main kernel instead of leaving it as a module.

As for the initramfs support, hpa has assured me that his klibc
distribution already has a full solution for NFS mounting on current
kernels.

Trond


  reply	other threads:[~2006-12-03  2:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 19:03 William Estrada
2006-12-02 19:07 ` Jan Engelhardt
2006-12-02 21:15   ` Willy Tarreau
2006-12-02 21:56     ` Jan Engelhardt
2006-12-02 22:55       ` Willy Tarreau
2006-12-03  2:37         ` Trond Myklebust [this message]
2006-12-03  6:02           ` Willy Tarreau
2006-12-03  7:05             ` Trond Myklebust
2006-12-03  8:30               ` Willy Tarreau
2006-12-03 11:04                 ` Jan Engelhardt
2006-12-03 16:59                 ` Trond Myklebust
2006-12-04 11:51 ` Janne Karhunen
2006-12-04 15:29   ` Trond Myklebust
2006-12-04 17:12     ` Janne Karhunen
2006-12-04 18:21       ` Trond Myklebust
2006-12-04 20:05         ` Janne Karhunen
2006-12-04 21:27           ` Trond Myklebust
2006-12-05  0:20             ` H. Peter Anvin
2006-12-04 20:03       ` Jan Engelhardt
2006-12-04 20:27         ` Janne Karhunen
2006-12-04 20:47         ` Trond Myklebust
2006-12-05 18:43           ` Jan Engelhardt
2006-12-05 19:37             ` Trond Myklebust
2006-12-05 19:59               ` Jan Engelhardt
2006-12-05 20:12                 ` Trond Myklebust
2007-01-27 14:47                   ` Jan Engelhardt
2006-12-07 22:27   ` Hans-Peter Jansen

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=1165113438.5698.5.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=MrUmunhum@popdial.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®