From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Warn people that ipchains and ipfwadm are going away.
Date: Tue, 21 Sep 2004 13:57:14 -0400 [thread overview]
Message-ID: <cippij$g5l$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <1095721742.5886.128.camel@bach>
Rusty Russell (IBM) wrote:
> Name: Warn that ipchains and ipfwadm are going away
> Status: Trivial
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>
> At the recent netfilter workshop in Erlangen, we was decided to remove
> the backwards compatibility code for ipchains and ipfwadm. This will
> allow significant cleanup of interfaces, since we had to have a
> mid-level interface for the backwards compatibility layer to use.
>
> Start off with a warning for 2.6.9, so any remaining users have a
> chance to migrate. Their firewall scripts might not check return
> values, and they might get a nasty surprise when this goes away.
I thought I understood the "new development model" but I guess I don't.
Are working features now going to be removed from the "stable" chain
instead of during a development cycle?
Not a complaint, I thought the new method was regarding new features...
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-09-21 17:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 23:09 [PATCH] Warn people that ipchains and ipfwadm are going away Rusty Russell (IBM)
2004-09-21 12:36 ` Marc Ballarin
2004-09-21 21:58 ` Rusty Russell
2004-09-21 22:36 ` Marc Ballarin
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 [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
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='cippij$g5l$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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