All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amin Azez <azez@ufomechanic.net>
To: Patrick McHardy <kaber@trash.net>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
	Netfilter Developer Mailing List
	<netfilter-devel@lists.netfilter.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Hendrik Nordstrom <henrik@henriknordstrom.net>
Subject: Re: NF structural changes (was: dangerous?)
Date: Wed, 14 Mar 2007 22:29:01 +0000	[thread overview]
Message-ID: <45F8772D.4070401@ufomechanic.net> (raw)
In-Reply-To: <45F870E3.6020805@trash.net>

Patrick McHardy wrote:
> Jan Engelhardt wrote:
>   
>> Right. Of course this is a problem. To that end, I can really only say
>> that a divide needs to be made someday.
>>     
>
> I totally disagree. iptables has tons of problems, I'm guessing that
> a year from now we will have a successor. Breaking compatibility at
> this point in its lifetime is not acceptable, especially on such a
> fundamental level. 
quite likely we will come to that conclusion but our discussion might 
result in private patches that don't hit the kernel.
> I really wish people would stop wasteing time
> trying to redesign iptables, its just not worth it.
>   
maybe, but it looks so promising coming from a position of wasting time 
trying to work with it :-)
- and you know it's so much more fun to tweak someone elses work than 
start from scratch...

Sam

  reply	other threads:[~2007-03-14 22:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 20:57 NF structural changes (was: dangerous?) Jan Engelhardt
2007-03-14 21:05 ` Patrick McHardy
2007-03-14 21:23   ` Jan Engelhardt
2007-03-14 21:48     ` Amin Azez
2007-03-15  2:24       ` Jan Engelhardt
2007-03-15  9:09         ` Henrik Nordstrom
2007-03-14 22:02     ` Patrick McHardy
2007-03-14 22:29       ` Amin Azez [this message]
2007-03-14 21:41 ` Krzysztof Oledzki
2007-03-14 21:49   ` Jan Engelhardt

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=45F8772D.4070401@ufomechanic.net \
    --to=azez@ufomechanic.net \
    --cc=henrik@henriknordstrom.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kaber@trash.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@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.