From: Jim Gifford <maillist@jg555.com>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Netfilter Developer <netfilter-devel@lists.netfilter.org>
Subject: Re: Use of Kernel Headers
Date: Wed, 18 Aug 2004 14:01:09 -0700 [thread overview]
Message-ID: <4123C395.8080402@jg555.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408182250390.23616@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Wed, 18 Aug 2004, Jim Gifford wrote:
>
>> Doesn't patch-o-matic update the ones in iptables-version/include/linux?
>
>
> Nope.
>
>> So the the kernel and the iptables are built from the same headers?
>> (Is this desired)
>
>
> Today yes, and probably desired while building with patch-o-matic
> patches applied.
>
>> Or would it benefit iptables to include all the updated headers in
>> iptables-version/include/linux?
>
>
> This would make things more clean cut separation between kernel and
> userspace.
>
> Regards
> Henrik
>
So now what do we do to get these changes made, or is it going to be a
distro specific thing?
--
----
Jim Gifford
maillist@jg555.com
next prev parent reply other threads:[~2004-08-18 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 21:10 Use of Kernel Headers Jim Gifford
2004-08-17 23:32 ` Henrik Nordstrom
2004-08-18 5:36 ` Jim Gifford
2004-08-18 19:00 ` Henrik Nordstrom
2004-08-18 19:25 ` Jim Gifford
2004-08-18 20:03 ` Henrik Nordstrom
2004-08-18 20:48 ` Jim Gifford
2004-08-18 20:51 ` Henrik Nordstrom
2004-08-18 21:01 ` Jim Gifford [this message]
2004-08-18 22:30 ` Jozsef Kadlecsik
2004-08-21 6:47 ` Jim Gifford
2004-08-21 9:30 ` Henrik Nordstrom
2004-08-21 14:53 ` Tobias DiPasquale
2004-08-21 15:13 ` Henrik Nordstrom
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 20:40 Jim Gifford
2004-08-17 21:00 ` Antony Stone
2004-08-17 21:09 ` Jim Gifford
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=4123C395.8080402@jg555.com \
--to=maillist@jg555.com \
--cc=hno@marasystems.com \
--cc=netfilter-devel@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 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.