From: Joe <joeja@mindspring.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.18 and RH 7.2
Date: Wed, 27 Feb 2002 14:49:10 -0800 [thread overview]
Message-ID: <3C7D6266.CFFDC7A3@mindspring.com> (raw)
In-Reply-To: <E16gBMx-0005rt-00@the-village.bc.nu>
Unfortunately it is not just warnings. It does not allow the firewall /
packet filter to start and iptables -L shows an open system as the rules were
never applied. Needless to say I'm back on 2.4.17.
Maybe I should file this as a bug with RH 7.2 then......
> > iptables 1.2.4 was rebuild for the 2.4.17 because it stopped working at
> > that point. I hope it isn't requirement to rebuild iptables against each
> > stable kernel release.
>
> Its not a requirement for 1.2.4 and 2.4.18 either - what happened was that
> some people (Red Hat notably) turned all the paranoid debugging stuff on
> and that is what spews the warnings.
next prev parent reply other threads:[~2002-02-27 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 18:27 kernel 2.4.18 and RH 7.2 Joe
2002-02-27 20:26 ` Russell King
2002-02-27 21:12 ` Alan Cox
2002-02-27 22:49 ` Joe [this message]
2002-02-27 21:17 ` Lukasz Trabinski
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=3C7D6266.CFFDC7A3@mindspring.com \
--to=joeja@mindspring.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.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