From: Jim Gifford <maillist@jg555.com>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Use of Kernel Headers
Date: Tue, 17 Aug 2004 14:09:27 -0700 [thread overview]
Message-ID: <41227407.1030406@jg555.com> (raw)
In-Reply-To: <200408172200.07018.Antony@Soft-Solutions.co.uk>
Antony Stone wrote:
>On Tuesday 17 August 2004 9:40 pm, Jim Gifford wrote:
>
>
>
>>I have been asked this question a lot of times, and I think it should be
>>asked here for an official answer.
>>
>>It has been stated numerous times that userspace programs should not be
>>compiled against raw kernel headers, but iptables does compile against
>>userspace headers and breaks this rule. With the advent of the
>>linux-libc-headers package, should iptables be compiled against the
>>linux-libc-headers or the raw kernel headers since iptables is a user
>>space program?
>>
>>Should patch-o-matic update the headers in the proper location,
>>/usr/include/linux/netfilter_ipv4 etc?
>>
>>
>
>Patch-o-matic is not the right way of doing this - this would be dealt with in
>a new version release of iptables.
>
>P-o-M is for adding new features and functions (which are optional and not
>used by most iptables users) to netfilter; it couldn't sensibly be used to
>change the structure of how it compiles.
>
>As for the answer to your question, I think that is one for the developers'
>list. Some of them do read this list, but cannot be guaranteed to see all
>posts or respond to them due to the volume.
>
>Regards,
>
>Antony.
>
>
>
Thanx Anthony, will do.
--
----
Jim Gifford
maillist@jg555.com
prev parent reply other threads:[~2004-08-17 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 20:40 Use of Kernel Headers Jim Gifford
2004-08-17 21:00 ` Antony Stone
2004-08-17 21:09 ` Jim Gifford [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=41227407.1030406@jg555.com \
--to=maillist@jg555.com \
--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