From: Mr Dash Four <mr.dash.four@googlemail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: xtables does not reconise ipportiphash/ipportnethash sets
Date: Thu, 23 Sep 2010 11:48:46 +0100 [thread overview]
Message-ID: <4C9B308E.5010804@googlemail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1009231224340.27002@obet.zrqbmnf.qr>
>>> I wonder. F13 ships with linux-glibc-devel-2.6.33, F14A with -2.6.35. So where
>>> is the actual issue? Nevertheless, I have devised a workaround for 2.6.34
>>> headers. Check out xt-a's b5e2c7255a87f3d981968e21ea7f88401fe8f8ad and let me
>>> know.
>>>
>>>
>> On my system it shows glibc-devel-2.12-3 (I don't have linux-glibc-devel).
>>
>
> It's called kernel-headers in Fedora. (Reason for it being called
> elsewhere is that some noobs spout out "you need kernel headers to build
> modules" and another noob installs kernel-headers rather than
> kernel-devel-XYZ.)
>
So, in other words I should be looking for kernel-devel (I am sure I've
got that)? Also, how do I 'check out xt-a's
b5e2c7255a87f3d981968e21ea7f88401fe8f8ad'?
next prev parent reply other threads:[~2010-09-23 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 19:19 xtables does not reconise ipportiphash/ipportnethash sets Mr Dash Four
2010-09-22 20:27 ` Jan Engelhardt
2010-09-22 23:23 ` Mr Dash Four
2010-09-23 0:03 ` Mr Dash Four
2010-09-23 0:18 ` Jan Engelhardt
2010-09-23 0:30 ` Mr Dash Four
2010-09-23 0:55 ` Jan Engelhardt
2010-09-23 1:01 ` Mr Dash Four
2010-09-23 10:28 ` Jan Engelhardt
2010-09-23 10:48 ` Mr Dash Four [this message]
2010-09-23 10:57 ` Jan Engelhardt
2010-09-23 11:21 ` Mr Dash Four
2010-09-23 12:16 ` Jan Engelhardt
2010-09-23 12:21 ` Mr Dash Four
2010-09-23 12:24 ` Jan Engelhardt
2010-09-23 12:31 ` Mr Dash Four
2010-09-23 12:49 ` Mr Dash Four
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=4C9B308E.5010804@googlemail.com \
--to=mr.dash.four@googlemail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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.