From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Scott van Looy <scott@ethosuk.org.uk>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: iptables 1.2.7a and kernel 2.4.19
Date: 17 Sep 2002 19:47:03 +0200 [thread overview]
Message-ID: <1032284823.30153.19.camel@tux> (raw)
In-Reply-To: <Pine.LNX.4.44.0209171400480.3423-100000@fire.ethosuk.org.uk>
On Tue, 2002-09-17 at 15:03, Scott van Looy wrote:
> Yet when I did this this morning on a different machine it worked fine,
> same pom, same kernel, same iptables builds
>
> Any ideas where I could start to look to see what's wrong?
You can start by getting a newer patch-o-matic.
ftp://ftp.netfilter.org/pub/patch-o-matic/snapshot/
This problem was fixed in cvs 020826 :)
--
/Martin
Never argue with an idiot. They drag you down to their level, then beat
you with experience.
next prev parent reply other threads:[~2002-09-17 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 13:03 iptables 1.2.7a and kernel 2.4.19 Scott van Looy
2002-09-17 17:47 ` Martin Josefsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-17 14:46 Rob Sterenborg
2002-09-17 15:56 ` Scott van Looy
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=1032284823.30153.19.camel@tux \
--to=gandalf@wlug.westbo.se \
--cc=netfilter@lists.netfilter.org \
--cc=scott@ethosuk.org.uk \
/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