All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Lim <vincent.lim@nestac.com>
To: Mladen Meduric <mladen_meduric@yahoo.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: patching iptables - how?
Date: Thu, 09 Jan 2003 10:11:44 +0800	[thread overview]
Message-ID: <3E1CDA60.D0512E54@nestac.com> (raw)
In-Reply-To: 20030108221616.1503.qmail@web12706.mail.yahoo.com

Mladen Meduric wrote:
> 
> Hi all,
> 
> just joined the list.
> Pretty new to linux/iptables (on SuSE8.0). I'm trying to patch from 1.2.5
> to 1.2.6a and then to 1.2.7a.

Why not just use 1.2.7a instead?
Anyway, the patch command should be like this:
# cd /path/to/iptables/source
# patch -p1 < /path/to/patch

Do this for all remaining patches.

> Do have all patches. Tried "patch" command, but I seem can't figure it out
> properly. Would someone explain how to do this in couple of steps, please?
> Also, from reading other articles, after patching up or reinstalling
> iptables from scratch, is it necessary to recompile the kernel?

In most cases (AFAIK), no. If you're using the same kernel during the
compilation (of iptables), iptables will reference whatever libraries
that exist for the current kernel. If you decide to switch kernels, you
probably might need to recompile iptables as certain libraries might
have underwent a significant tweak/hack/modification and might render
iptables in-operable.

-- 
Vincent Lim
Software Engineer
NESTAC Solution Sdn Bhd
vincent.lim@nestac.com | +(6012) 659-6609


  parent reply	other threads:[~2003-01-09  2:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 22:16 patching iptables - how? Mladen Meduric
2003-01-09  1:24 ` Athan
2003-01-09  2:11 ` Vincent Lim [this message]
2003-01-09  2:34 ` Fabrice MARIE
2003-01-09  3:42   ` Mladen Meduric
2003-01-09 16:22     ` Arnt Karlsen

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=3E1CDA60.D0512E54@nestac.com \
    --to=vincent.lim@nestac.com \
    --cc=mladen_meduric@yahoo.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 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.