mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@kabuki.openfridge.net>
To: mirabilos <eccesys@topmail.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CML 1 is ok
Date: Sat, 19 May 2001 09:09:39 +1000	[thread overview]
Message-ID: <20010519090939.A675@kabuki.openfridge.net> (raw)
In-Reply-To: <20010518220028.B139BA5AD65@www.topmail.de>
In-Reply-To: <20010518220028.B139BA5AD65@www.topmail.de>; from eccesys@topmail.de on Sat, May 19, 2001 at 12:00:28AM +0200

On Sat, May 19, 2001 at 12:00:28AM +0200, mirabilos wrote:
> netfilter: I _liked_ ipfwadm
> because I hate to always re-learn when a new kernel comes out.

Netfilter is going to stay. Rusty knew from early on in ipchains development
that the whole concept was wrong, but Alan told him to continue on, get it
into 2.2, and then do a new one for 2.4. There's a document detailing this
somewhere, I just can't forget where.

> our company will soon ship a product still using ipfwadm (I
> started with 2.0.33, going to .36 and 2.4.0-testX).
> It's a pity this M$ism to not support it forever (they just
> stopped supporting DOS! and GW-BASIC *snief*)

This is entirely incorrect and FUD. If enable Netfilter, look in the
Netfilter options, disable conntrack and IP tables support, you have
(*gasp!*) ipchains compatability, as well as (*ohmygod!*) ipfwadm
compatability.
 
> -mirabilos
> 
> PS: Don't answer plz as I'll be offline for a time.
>     _And_ I mean this honest, even it might considered sp.m

The FUD has to be corrected.

-- 
Daniel Stone
daniel@kabuki.openfridge.net

      reply	other threads:[~2001-05-18 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 22:00 mirabilos
2001-05-18 23:09 ` Daniel Stone [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=20010519090939.A675@kabuki.openfridge.net \
    --to=daniel@kabuki.openfridge.net \
    --cc=eccesys@topmail.de \
    --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

all inboxes | Powered by JetHome®