linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Schwenke" <martin@meltin.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Pull NFS server address off root_server_path
Date: Fri, 13 Sep 2002 10:28:29 +1000	[thread overview]
Message-ID: <200209130032.KAA32528@thucydides.inspired.net.au> (raw)
In-Reply-To: <1031818177.2994.39.camel@irongate.swansea.linux.org.uk>

>>>>> "Alan" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

    Alan> You are probably much better using the initrd based dhcp
    Alan> client from things like the LTSP project (ltsp.org) than the
    Alan> kernel one

That's probably true in the long term.  For the short term, is the
initrd-based stuff working right now?  I didn't think it was quite
there yet...

If the patch goes in now, I won't be terribly disappointed if it comes
back out, along with (most of) the rest of the ipconfig stuff, if the
initrd-based stuff works acceptably before the feature freeze...

I would think that if there's a chance that the ipconfig stuff will
stay in for 2.6, and this patch improves it, then it should probably
be merged.  The patch has been in use at OzLabs for about 6 months
(since I moved the DHCP server off the NFS server :-) to help boot the
embedded boxes that David Gibson is doing bring-up work on.

peace & happiness,
martin

  reply	other threads:[~2002-09-13  0:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  2:08 [PATCH] Pull NFS server address off root_server_path Martin Schwenke
2002-09-12  8:09 ` Alan Cox
2002-09-13  0:28   ` Martin Schwenke [this message]
2002-09-13  1:31     ` David Gibson
2002-09-16  8:32       ` Rob Landley
2002-09-13 13:14     ` Alan Cox

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=200209130032.KAA32528@thucydides.inspired.net.au \
    --to=martin@meltin.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=trond.myklebust@fys.uio.no \
    /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).