From: Mohamed Eldesoky <eldesoky.lists@gmail.com>
To: "Hill, John" <jhill@columbuscontainer.com>,
netfilter <netfilter@lists.netfilter.org>
Subject: Re: Iptables 2.4x kernels
Date: Tue, 15 Mar 2005 10:34:10 +0200 [thread overview]
Message-ID: <1403218a0503150034643cc884@mail.gmail.com> (raw)
In-Reply-To: <E2FF7089130F614EACAB856B5582C9FD3CCCFC@exchange.columbuscontainer.com>
Why I get this email soooooooooooooooo many times !!!!
On Fri, 11 Mar 2005 12:34:53 -0500, Hill, John
<jhill@columbuscontainer.com> wrote:
> Should I consider iptables to be dropping 2.4.x kernel support?
>
> I have yet to compile iptables successfully since 2.4.26 and 1.2.11. I
> get a MUTEX error. This was addressed by a patch (sent to me in email)
> but a permanent fix has failed to make the kernel and the iptables code.
> The new 2.4.29 and 1.3.1 still does it. I also had segmentation errors
> with shorewall after applying the patch to 2.4.28 and 1.3.0. I gave up
> without looking into the problem further hoping the new kernel and
> iptables would fix it. It has not.
>
> Thanks
>
> --john
>
>
--
Mohamed Eldesoky
www.eldesoky.net
RHCE
prev parent reply other threads:[~2005-03-15 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 17:34 Iptables 2.4x kernels Hill, John
2005-03-15 8:34 ` Mohamed Eldesoky [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=1403218a0503150034643cc884@mail.gmail.com \
--to=eldesoky.lists@gmail.com \
--cc=jhill@columbuscontainer.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 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.