From: Krzysztof Rusocki <kszysiu@main.braxis.co.uk>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Make IP-Config work without ip= supplied
Date: Mon, 18 Feb 2002 23:24:51 +0100 [thread overview]
Message-ID: <20020218222451.GA23899@main.braxis.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
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.
Cheers,
Krzysztof
PS
please CC, not a subscriber.
PS2
this was also sent to linux-net but got spamfiltered, i suppose
(checked on marc.theaimsgroup.com)
[-- Attachment #2: ipconfig.c.diff-2.4.18-rc1 --]
[-- Type: text/plain, Size: 393 bytes --]
--- linux/net/ipv4/ipconfig.c~ Sun Feb 17 20:29:00 2002
+++ linux/net/ipv4/ipconfig.c Sun Feb 17 20:35:27 2002
@@ -102,7 +102,7 @@
*/
int ic_set_manually __initdata = 0; /* IPconfig parameters set manually */
-int ic_enable __initdata = 0; /* IP config enabled? */
+int ic_enable __initdata = 1; /* IP config enabled? */
/* Protocol choice */
int ic_proto_enabled __initdata = 0
[-- Attachment #3: ipconfig.c.diff-2.2.20 --]
[-- Type: text/plain, Size: 353 bytes --]
--- linux/net/ipv4/ipconfig.c.orig Sun Mar 25 18:31:12 2001
+++ linux/net/ipv4/ipconfig.c Sun Feb 17 20:42:32 2002
@@ -87,7 +87,7 @@
* Public IP configuration
*/
-int ic_enable __initdata = 0; /* IP config enabled? */
+int ic_enable __initdata = 1; /* IP config enabled? */
/* Protocol choice */
static int ic_proto_enabled __initdata = 0
next reply other threads:[~2002-02-18 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 22:24 Krzysztof Rusocki [this message]
2002-02-18 22:34 ` 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=20020218222451.GA23899@main.braxis.co.uk \
--to=kszysiu@main.braxis.co.uk \
--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
all inboxes | Powered by JetHome®