From: Wilmer van der Gaast <lintux@lintux.cx>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Configuration help texts for IPsec
Date: Mon, 17 Nov 2003 15:57:23 +0100 [thread overview]
Message-ID: <20031117145723.GB1268@gaast.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0311170948100.1445-100000@thoron.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
James Morris (jmorris@redhat.com) wrote:
> > IPsec-related options say "Say Y unless you know what you are doing.".
> > Looks fine for people who applied the IPsec patch to a kernel which
> > comes without it, but now that it's in stock, it's probably not very
> > useful to force all users to use IPsec.
> Nobody is being forced to use it: the advice is provided to help people
> get IPsec working properly.
>
Yes, very true. But now that the patch is in 2.6 by default, I think the
situation changes.
Just imagine a person who doesn't even know what IPsec is, trying to
configure a 2.6 kernel. "IP: AH tranformation.. What's that? Let's check
the help page. Oh, it says I should just say Yes. Okay, let's do that."
Shouldn't the text "If unsure, say Y." be more like "If you want to use
IPsec, you need this."? Possibly with an addition like "If you don't
know what IPsec is, you don't need it."?
Greetings,
Wilmer v/d Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| lintux : :' : lintux.cx | | OSS Programmer www.bitlbee.org |
| at `. `~' debian.org | | www.algoritme.nl www.lintux.cx |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-17 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-15 15:08 Wilmer van der Gaast
2003-11-17 14:49 ` James Morris
2003-11-17 14:57 ` Wilmer van der Gaast [this message]
2003-11-17 15:07 ` Valdis.Kletnieks
2003-11-20 0:45 ` Eric Sandall
2003-12-14 15:55 ` Florian Weimer
2003-12-14 21:13 ` coderman
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=20031117145723.GB1268@gaast.net \
--to=lintux@lintux.cx \
--cc=jmorris@redhat.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
all inboxes | Powered by JetHome®