From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: torvalds@osdl.org, netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] Warn people that ipchains and ipfwadm are going away.
Date: Wed, 22 Sep 2004 00:36:46 +0200 [thread overview]
Message-ID: <20040922003646.3a84f4c5.Ballarin.Marc@gmx.de> (raw)
In-Reply-To: <1095803902.1942.211.camel@bach>
On Wed, 22 Sep 2004 07:58:22 +1000
Rusty Russell <rusty@rustcorp.com.au> wrote:
> Sure, but you have to start somewhere. Next step will be #error. Then
> finally remove the whole thing (I don't want to remove the whole thing
> to start with, since that would create a silent failure).
I was rather thinking of some prominent printks at module init time.
People using distro kernels will never see compile time warnings.
I just added some warnings, but modprobe ipchains always fails on
2.6.9-rc2:
FATAL: Error inserting ipchains
(/lib/modules/2.6.9-rc2-rcf/kernel/net/ipv4/netfilter/ipchains.ko): Device
or resource busy
in log buffer:
ip_conntrack version 2.1 (8191 buckets, 65528 max) - 332 bytes per
conntrack
Unable to register netfilter socket option
Am I missing something?
Regards
next prev parent reply other threads:[~2004-09-21 22:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 23:09 Rusty Russell (IBM)
2004-09-21 12:36 ` Marc Ballarin
2004-09-21 21:58 ` Rusty Russell
2004-09-21 22:36 ` Marc Ballarin [this message]
2004-09-21 22:36 ` David S. Miller
2004-09-21 23:35 ` Marc Ballarin
2004-09-22 0:16 ` Patrick McHardy
2004-09-22 13:37 ` Marc Ballarin
2004-09-22 13:58 ` Jesper Juhl
2004-09-22 14:13 ` Richard B. Johnson
2004-09-22 11:36 ` Richard B. Johnson
2004-09-22 11:47 ` Martin Josefsson
2004-09-22 12:05 ` Richard B. Johnson
2004-09-22 12:41 ` Gene Heskett
2004-09-22 14:19 ` Fao, Sean
2004-09-22 15:31 ` William Stearns
2004-09-22 11:52 ` James Courtier-Dutton
2004-09-22 11:55 ` Marc Ballarin
2004-09-21 17:57 ` Bill Davidsen
[not found] <2GFBZ-61e-11@gated-at.bofh.it>
[not found] ` <2GSfS-6eW-5@gated-at.bofh.it>
[not found] ` <2H0ZO-49v-13@gated-at.bofh.it>
[not found] ` <2HdDL-48z-53@gated-at.bofh.it>
[not found] ` <2HdNp-4eJ-27@gated-at.bofh.it>
2004-09-22 12:15 ` Andi Kleen
2004-09-22 14:04 ` David Woodhouse
2004-09-23 18:07 Albert Cahalan
2004-09-23 19:33 ` Chris Friesen
2004-09-23 19:36 ` Albert Cahalan
2004-09-23 19:57 ` Andy Lutomirski
2004-09-23 19:57 ` David S. Miller
2004-09-23 23:08 ` Matthew Garrett
2004-09-23 23:25 ` David S. Miller
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=20040922003646.3a84f4c5.Ballarin.Marc@gmx.de \
--to=ballarin.marc@gmx.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome