From: Adrian Bunk <bunk@fs.tum.de>
To: netdev@oss.sgi.com, davem@redhat.com, pekkas@netcore.fi
Cc: lksctp-developers@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: RFC: [2.6 patch] disallow modular IPv6
Date: Mon, 29 Sep 2003 00:59:41 +0200 [thread overview]
Message-ID: <20030928225941.GW15338@fs.tum.de> (raw)
It seems modular IPv6 doesn't work 100% reliable, e.g. after looking at
the code it doesn't seem to be a good idea to compile a kernel without
IPv6 support and later build and install IPv6 modules. Is there a great
need for modular IPv6 or is the patch below to disallow modular IPv6 OK?
diffstat output:
net/Kconfig | 2 +-
net/sctp/Kconfig | 6 ------
2 files changed, 1 insertion(+), 7 deletions(-)
cu
Adrian
--- linux-2.6.0-test6-full/net/Kconfig.old 2003-09-29 00:53:05.000000000 +0200
+++ linux-2.6.0-test6-full/net/Kconfig 2003-09-29 00:55:55.000000000 +0200
@@ -117,7 +117,7 @@
# IPv6 as module will cause a CRASH if you try to unload it
config IPV6
- tristate "The IPv6 protocol (EXPERIMENTAL)"
+ bool "The IPv6 protocol (EXPERIMENTAL)"
depends on INET && EXPERIMENTAL
---help---
This is experimental support for the next version of the Internet
--- linux-2.6.0-test6-full/net/sctp/Kconfig.old 2003-09-29 00:50:11.000000000 +0200
+++ linux-2.6.0-test6-full/net/sctp/Kconfig 2003-09-29 00:52:55.000000000 +0200
@@ -5,14 +5,8 @@
menu "SCTP Configuration (EXPERIMENTAL)"
depends on INET && EXPERIMENTAL
-config IPV6_SCTP__
- tristate
- default y if IPV6=n
- default IPV6 if IPV6
-
config IP_SCTP
tristate "The SCTP Protocol (EXPERIMENTAL)"
- depends on IPV6_SCTP__
---help---
Stream Control Transmission Protocol
next reply other threads:[~2003-09-28 22:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:59 Adrian Bunk [this message]
2003-09-28 23:18 ` RFC: [2.6 patch] disallow modular IPv6 Arnaldo Carvalho de Melo
2003-09-28 23:24 ` Adrian Bunk
2003-09-28 23:39 ` Arnaldo Carvalho de Melo
2003-09-28 23:47 ` Arnaldo Carvalho de Melo
2003-09-29 0:14 ` Adrian Bunk
2003-09-29 0:32 ` Arnaldo Carvalho de Melo
2003-09-29 9:02 ` David Woodhouse
2003-09-29 14:15 ` Arnaldo Carvalho de Melo
2003-09-29 14:28 ` Jan Evert van Grootheest
2003-09-29 14:29 ` David Woodhouse
2003-09-29 14:38 ` Valdis.Kletnieks
2003-09-29 14:46 ` David Woodhouse
2003-09-30 5:17 ` David S. Miller
2003-09-30 6:31 ` David Woodhouse
2003-10-01 19:47 ` Guennadi Liakhovetski
2003-09-30 5:11 ` David S. Miller
2003-09-30 13:37 ` Adrian Bunk
2003-09-30 15:04 ` Arnaldo Carvalho de Melo
2003-10-01 6:39 ` David S. Miller
2003-09-30 5:09 ` David S. Miller
2003-09-30 6:32 ` David Woodhouse
2003-09-30 7:03 ` David S. Miller
2003-09-30 7:39 ` David Woodhouse
2003-09-30 8:08 ` David S. Miller
2003-09-30 8:26 ` David Woodhouse
2003-09-30 8:30 ` David S. Miller
2003-09-30 8:42 ` David Woodhouse
2003-09-30 8:51 ` David S. Miller
2003-09-30 9:14 ` David Woodhouse
2003-09-30 9:17 ` David Woodhouse
2003-09-30 9:24 ` David S. Miller
2003-09-30 9:57 ` Sam Ravnborg
2003-09-30 10:02 ` David Woodhouse
2003-09-30 10:01 ` David S. Miller
2003-09-30 10:14 ` David Woodhouse
2003-09-30 11:39 ` Sam Ravnborg
2003-09-30 13:44 ` Dana Lacoste
2003-09-30 13:50 ` Kai Germaschewski
2003-09-30 15:13 ` Richard Guy Briggs
2003-09-30 14:21 ` Theodore Ts'o
2003-09-30 14:51 ` David Woodhouse
2003-09-30 12:06 ` Olivier Galibert
2003-09-29 6:29 ` Pekka Savola
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=20030928225941.GW15338@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.