From: David Ford <david+challenge-response@blue-labs.org>
To: Andrew Walrond <andrew@walrond.org>
Cc: netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: Iptables-1.2.9/10 compile failure with linux 2.6.7 headers
Date: Fri, 18 Jun 2004 12:39:54 -0400 [thread overview]
Message-ID: <40D31ADA.3080204@blue-labs.org> (raw)
In-Reply-To: <200406181721.47968.andrew@walrond.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
The current linux libc headers package is much more frequently updated
and closely matches released kernels. LLH is a sanitized linux headers
package and is currently based on 2.6.6 headers.
Yes you can build iptables on 2.6.6 for a 2.6.7 kernel. I have built
iptables once or twice a year and built kernels once or twice a week.
Iptables continues to work fine.
David
Andrew Walrond wrote:
>Hi David,
>
>On Friday 18 Jun 2004 17:10, David Ford wrote:
>
>
>>Iptables should be using linux-libc-headers headers instead of kernel
>>headers.
>>
>>
>
>Is this acquired knowledge, or new Netfilter policy?
>How dependant are the iptables tools on the specifc kernel running?
>
>Ie
>Can I build iptables for use on 2.6.7 kernel with 2.6.6 linux-libc-headers?
>(probably)
>
>But could I build iptables for 2.6.7 kernel with 2.4.20 linux-libc-headers?
>(probably not?)
>
>The INSTALL file states specifically to use
>KERNEL_DIR=<<where-you-built-your-kernel>>
>
>Andrew
>
>
[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]
begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2004-06-18 16:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 15:11 Iptables-1.2.9/10 compile failure with linux 2.6.7 headers Andrew Walrond
2004-06-18 16:10 ` David Ford
2004-06-18 16:21 ` Andrew Walrond
2004-06-18 16:39 ` David Ford [this message]
2004-06-18 16:56 ` Kalin KOZHUHAROV
2004-06-18 17:18 ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-18 18:36 ` Kalin KOZHUHAROV
2004-06-18 22:51 ` YOSHIFUJI Hideaki / 吉藤英明
[not found] ` <200406191038.51118.andrew@walrond.org>
2004-06-19 16:35 ` YOSHIFUJI Hideaki / 吉藤英明
2004-06-19 18:59 ` David S. Miller
2004-06-18 17:46 ` Andrew Walrond
2004-06-18 18:35 ` Kalin KOZHUHAROV
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=40D31ADA.3080204@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.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