From: Bill Fink <billfink@mindspring.com>
To: Joerg Roedel <joro-lkml@zlug.org>
Cc: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH 01/02] net/ipv6: seperate sit driver to extra module
Date: Sat, 7 Oct 2006 01:05:16 -0400 [thread overview]
Message-ID: <20061007010517.3b9db240.billfink@mindspring.com> (raw)
In-Reply-To: <20061006151556.GA15637@zlug.org>
On Fri, 6 Oct 2006 17:15:56 +0200, Joerg Roedel wrote:
> +config IPV6_SIT
> + tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
> + depends on IPV6
> + default y
> + ---help---
> + Tunneling means encapsulating data of one protocol type within
> + another protocol and sending it over a channel that understands the
> + encapsulating protocol. This driver implements encapsulation of IPv6
> + into IPv4 packets. This is useful if you want to connect two IPv6
> + networks over an IPv4-only path.
> +
> + Saying M here will produce a module called sit.ko. If unsure, say N.
>From a user perspective, I believe it should say "If unsure, say Y".
The unsure case for the unsure user should be the case that works for
the broadest possible usage spectrum, which would be the 'Y' case.
To put it another way, if you pick 'Y' and don't really need it, the
only downside is wasting some memory. But if you pick 'N' and actually
did need it, previously working IPv6 networking would no longer work.
I believe the default setting should match the unsure recommendation.
-Bill
next prev parent reply other threads:[~2006-10-07 5:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 9:34 [PATCH 01/02] net/ipv6: seperate sit driver to extra module Joerg Roedel
2006-10-06 11:38 ` Samuel Tardieu
2006-10-06 11:44 ` Peter Bieringer
2006-10-06 12:09 ` Joerg Roedel
2006-10-06 12:24 ` Samuel Tardieu
2006-10-06 12:59 ` YOSHIFUJI Hideaki / 吉藤英明
2006-10-06 15:15 ` Joerg Roedel
2006-10-07 5:05 ` Bill Fink [this message]
2006-10-07 5:32 ` James Morris
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=20061007010517.3b9db240.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=joro-lkml@zlug.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).