From: Valdis.Kletnieks@vt.edu
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: David Woodhouse <dwmw2@infradead.org>,
Adrian Bunk <bunk@fs.tum.de>,
netdev@oss.sgi.com, davem@redhat.com, pekkas@netcore.fi,
lksctp-developers@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: [2.6 patch] disallow modular IPv6
Date: Mon, 29 Sep 2003 10:38:30 -0400 [thread overview]
Message-ID: <200309291438.h8TEcVtH021550@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 29 Sep 2003 11:15:48 -0300." <20030929141548.GS1039@conectiva.com.br>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Mon, 29 Sep 2003 11:15:48 -0300, Arnaldo Carvalho de Melo said:
> Humm, so the user will have, in this case, these choices:
>
> 1. "I don't want IPV6 at all, not now, not ever":
> CONFIG_IPV6_SUPPORT=N
> CONFIG_IPV6=N (this is implicit as this depends on
> CONFIG_IPV6_SUPPORT)
>
> 2. "I think I may well want it the future, who knows? but not now...":
> CONFIG_IPV6_SUPPORT=Y
> CONFIG_IPV6=N
>
> 3. "Nah, some of the users of this pre-compiled kernel will need it":
> CONFIG_IPV6_SUPPORT=Y
> CONFIG_IPV6=M
>
> 4. "Yeah, IPV6 is COOL, how can somebody not use this piece of art?":
> CONFIG_IPV6_SUPPORT=Y
> CONFIG_IPV6=Y
>
> Isn't this confusing for the I-wanna-triple-my-kernel-performance-by-compiling-
> the-kernel-for-exactly-what-I-have hordes of users?
No, this is the behavior we want, and we can write Kconfig help entries that
explain it.
Anybody want to do a sanity check against CONFIG_IP6_NF_IPTABLES - that
looks like another gotcha if it isn't implemented properly (it may be, I just haven't
actually looked it over)?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-09-29 14:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 22:59 RFC: [2.6 patch] disallow modular IPv6 Adrian Bunk
2003-09-28 23:18 ` 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 [this message]
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=200309291438.h8TEcVtH021550@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=acme@conectiva.com.br \
--cc=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=dwmw2@infradead.org \
--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 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).