From: Tony Earnshaw <tonye@billy.demon.nl>
To: netfilter@lists.netfilter.org
Subject: FWIW
Date: Sun, 23 May 2004 14:40:33 +0200 [thread overview]
Message-ID: <1085316030.3072.23.camel@localhost> (raw)
Maybe it could help someone :)
RedHat RHEL3 ES
Kernel was kernel.org 2.6.4 + iptables 1.2.9, pom-ng-20040302
Wanted kernel 2.6.6, have it, it works with Netfilter pom-ng :)
But: pom-ng-20040302 had to be replaced with the CVS pom-ng tarball;
iptables had to be replaced with 1.2.10 (CVS tarball).
Setting make "KERNEL_DIR=" to the 2.6.6 source dir caused iptables (both
1.2.9 and 1.2.10) to abort the make, with all kinds of inconsistencies.
However, cheating by setting "KERNEL_DIR=" to the (obviously pom-ng
patched) 2.6.4 source worked. All the iptables kernel stuff works,
iptables libipt_* libraries all work. So I'm happy.
Unrelated to Netfilter: 'make xconfig' in Gnome 2.2 for the kernel
resulted in no fonts (just small "squares"), so I had to use 'make
menuconfig" for the first time. No skin off my nose, though.
Best, and thanks for a *fine* mailing list.
--Tonni
--
We make out of the quarrel with others rhetoric
but out of the quarrel with ourselves, poetry.
mail: tonni@billy.demon.nl
http://www.billy.demon.nl
reply other threads:[~2004-05-23 12:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1085316030.3072.23.camel@localhost \
--to=tonye@billy.demon.nl \
--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 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.