From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: ipset v6.latest bugs?
Date: Wed, 27 Apr 2011 22:40:02 +0100 [thread overview]
Message-ID: <4DB88D32.60207@googlemail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1104272323570.7833@blackhole.kfki.hu>
>> I think I understand it now, thanks for the explanation. I hope that you would
>> be able to fix this bug.
>>
>
> I'm attending an annual conference this week, so it seems I won't have
> time to work on the bugfix before the weekend, sorry.
>
No worries, I will be using 4.5 for the time being particularly as I was
finally able to integrate it into the kernel (your "patch_kernel" script
did the donkey work though :-) ) and I was also able to "convert" ipset
4.5 to use pkgconfig (still testing it though), so when I am more or
less done I will be in a position to build (and use!) both generation
packages as a standalone software.
> I don't really see why you have to split ipset from xtables-addons. What's
> wrong with the standalone ipset package, what forces you to do so?
>
I don't actually need xtables-addons for 80% of my boxes, so just
building the ipset package was perfect! On those machines I used to
compile xtables-addons just because I needed ipset, so it made more
sense to use ipset as standalone and save myself the hassle (and some
resources too).
I planned to do this for months, but wasn't able to due to time
constraints. I can now afford more time and I am glad I was able to
finally split it up. I am particularly pleased that I was able to
integrate it into the kernel, which saved me another headache of having
to deal with the bl**dy buildsys packages on Fedora which were needed to
build the kernel modules.
prev parent reply other threads:[~2011-04-27 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 11:55 ipset v6.latest bugs? Mr Dash Four
2011-04-25 20:03 ` Jozsef Kadlecsik
2011-04-25 20:36 ` Mr Dash Four
2011-04-25 21:51 ` Jozsef Kadlecsik
2011-04-26 0:38 ` Mr Dash Four
2011-04-26 13:57 ` Jozsef Kadlecsik
2011-04-26 15:04 ` Mr Dash Four
2011-04-26 23:18 ` Mr Dash Four
2011-04-27 7:15 ` Jozsef Kadlecsik
2011-04-27 12:00 ` Mr Dash Four
2011-04-27 21:27 ` Jozsef Kadlecsik
2011-04-27 21:40 ` Mr Dash Four [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=4DB88D32.60207@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=kadlec@blackhole.kfki.hu \
--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.