public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make IP-Config work without ip= supplied
Date: 18 Feb 2002 14:34:25 -0800	[thread overview]
Message-ID: <a4rvhh$vku$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020218222451.GA23899@main.braxis.co.uk>

Followup to:  <20020218222451.GA23899@main.braxis.co.uk>
By author:    Krzysztof Rusocki <kszysiu@main.braxis.co.uk>
In newsgroup: linux.dev.kernel
> 
> Hi,
> 
> Just noticed that IP-Config behavior when no ip= parm is used has changed in
> 2.2.18.
> 
> Up to 2.2.17 IP-Config was enabled even when ip= was omitted. I think that
> it's good for use in i.e. diskless nodes.
> 
> Since 2.2.18, IP-Config does nothing at all until ip= is passed to the
> kernel, however Documentation/nfsroot.txt still says that IP-Config is
> enabled by default. Was that intentional change?
> 
> Such behavior remains in both 2.2.20 and 2.4.18-rc1. Following patches
> (against these two kernel trees) make IP-Config enabled by default.
> 

I don't think this is a good idea.  The current behaviour should work
across the board.  Diskless nodes should use a diskless bootloader
which support command lines -- that way you get to specify the mode as
well.  *ALL* nodes should use the command line these days.

Can we get rid of the g----d bootsect.S, please?

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@zytor.com>

      reply	other threads:[~2002-02-18 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18 22:24 [PATCH] Make IP-Config work without ip= supplied Krzysztof Rusocki
2002-02-18 22:34 ` H. Peter Anvin [this message]

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='a4rvhh$vku$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --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