Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: netfilter@lists.netfilter.org
Subject: Re: ipt_random
Date: Wed, 20 Jul 2005 16:15:54 +0800	[thread overview]
Message-ID: <061001c58d03$3fdeee00$1280a8c0@newlife> (raw)
In-Reply-To: Pine.LNX.4.61.0507200953080.10223@yvahk01.tjqt.qr


From: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
> 
> >Too bad that's not how the patch-o-matic scripts are written. It will not
> >patch the kernel source, if it did not follow certain directory structure.
> >
> >That's how the patch-o-matic 'runme --batch' behaves, if what I have
> >tried is correct.
> 
> I usually dont use runme, because I'm almost sure it creates rejectfiles 
> nonetheless given the kernel I use. So I copy the files and merge the *.ladd 
> files by hand. Voil`a. Note that I do use ipt_random actively, so it 
> definitely works on 2.6.x.
> 

If you have small work  you could copy here and there. As soon as
you have a few patches to apply, it will become very laborious and
error proned. That's the whole purpose of 'runme'.

Any the contrary, I use 'runme' as it guarantees me certain minimum
repeatable quality.

Anyway, thanks for letting me know about the quality of the ipt_random.c
on 2.6 kernel. I actually found another patch, 

https://lists.netfilter.org/pipermail/ netfilter-devel/2004-November/017491.html 

Cheers.





  reply	other threads:[~2005-07-20  8:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19  9:25 ipt_random Ming-Ching Tiew
2005-07-19 10:17 ` ipt_random Jan Engelhardt
2005-07-20  1:17   ` ipt_random Ming-Ching Tiew
2005-07-20  6:25     ` ipt_random Jan Engelhardt
2005-07-20  7:08       ` ipt_random Ming-Ching Tiew
2005-07-20  7:54         ` ipt_random Jan Engelhardt
2005-07-20  8:15           ` Ming-Ching Tiew [this message]
2005-07-20  8:32         ` ipt_random Jozsef Kadlecsik

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='061001c58d03$3fdeee00$1280a8c0@newlife' \
    --to=mingching.tiew@redtone.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox