From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: Is there some reason why IPSET kernel modules are not in kernel source?
Date: Sun, 28 Feb 2010 00:37:56 -0600 [thread overview]
Message-ID: <20100228063756.GC10293@minipax> (raw)
In-Reply-To: <4B86B562.5050605@gatworks.com>
> On 02/24/2010 04:40 PM, Jozsef Kadlecsik wrote:
> >>Seems like iptable modules are included in kernel source.
> >>> Not so with the IPSET modules. Is this something political?
> >Nothing political. ipset needs to be rewritten before
> >submitting, in order to avoid backward-forward compatibility
> >issues in the future. That makes me say "no submitting yet".
On Thu, Feb 25, 2010 at 12:37:38PM -0500, U. George wrote:
> Is that the ipset kernel modules? Its been at least 4 years. Fedora
> et al just wont accept the program ipset until the iptable / ipset
> kernel mods are in the 'upstream' kernel source.
Then your solution is to package and compile it yourself. FWIW I do
think that there are numerous distributions which package ipset.
> Some reason as to why u cannot repair the ip_set kernel-modules
> as new kernels are released?
I would not ask such a thing. While I am sure you did not intend
this, it comes across as being ungrateful and demanding. Free
software contributors often are doing it on their own time. Be
thankful for what we have, and try to show it. :)
That said, I too will be grateful when ipset is ready for the
mainstream kernel. ;)
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
next prev parent reply other threads:[~2010-02-28 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 19:25 Is there some reason why IPSET kernel modules are not in kernel source? U. George
2010-02-24 21:40 ` Jozsef Kadlecsik
2010-02-25 17:37 ` U. George
2010-02-28 6:37 ` /dev/rob0 [this message]
2010-02-28 13:26 ` U. George
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=20100228063756.GC10293@minipax \
--to=rob0@gmx.co.uk \
--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 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).