From: Torsten Luettgert <ml-netfilter@enda.eu>
To: netfilter@vger.kernel.org
Cc: Jan Engelhardt <jengelh@inai.de>
Subject: Re: Best kernel version
Date: Tue, 20 Nov 2012 10:13:28 +0100 [thread overview]
Message-ID: <20121120101328.76e11aab@goldlack.enda.eu> (raw)
In-Reply-To: <alpine.LNX.2.01.1211172241450.24164@nerf07.vanv.qr>
On Sat, 17 Nov 2012 22:42:29 +0100 (CET)
Jan Engelhardt <jengelh@inai.de> wrote:
> On Saturday 2012-11-17 22:19, Giuseppe Longo wrote:
>
> >Hi,
> >what is the best kernel version to utilize with netfilter module?
>
> The ones from the future.
Jan,
it's perfectly ok for you to not like questions like these, or find
them ill-posed or even dumb. Still, sarcastic answers won't make anyone
happier and create a hostile, elitist climate. I'd suggest you just let
the less exalted listeners on this list - like me - handle this stuff
and concentrate on other questions.
@Giuseppe: that is a question with no simple answer. It all depends on
what you want to use. If you're after the most bleeding-edge features,
by all means use the latest kernels available.
If you're after more standard stuff, I'd suggest using one of the
"longtime support" kernels, like 3.0, 3.2 or 3.4. Bug fixes still enter
those trees, but potentially destabilizing new features don't, so
that's exactly what you'll want if you're after stability.
Hope that helps,
Torsten
prev parent reply other threads:[~2012-11-20 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 21:19 Best kernel version Giuseppe Longo
2012-11-17 21:42 ` Jan Engelhardt
2012-11-20 9:13 ` Torsten Luettgert [this message]
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=20121120101328.76e11aab@goldlack.enda.eu \
--to=ml-netfilter@enda.eu \
--cc=jengelh@inai.de \
--cc=netfilter@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 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.