All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@ncparty.dk>
To: <netfilter-devel@lists.netfilter.org>
Subject: CONNMARK Patching Problem
Date: Sat, 9 Nov 2002 12:43:08 +0100	[thread overview]
Message-ID: <005a01c287e5$2d0862a0$0200000a@parseerror.dk> (raw)

Hey! :D

I'm having a very anoying problem.

I have patched 2.4.18-19 kernels where both have the same problem, when i
run patch-o-magic on a fresh kernel, then when i come to where i can patch
the CONNMARK module into the kernel, it always fail, even if it's the only
thing i select, and with both kernels, even they both are fresh installed.

Testing... CONNMARK.patch NOT APPLIED ( 4 missing files)
The extra/CONNMARK patch:
   Author: Henrik Nordstrom <hno@marasystems.com>
   Status: working

<-Nice information about the module...-->

-----------------------------------------------------------------
Do you want to apply this patch [N/y/t/f/a/r/b/w/v/q/?] y
Testing patch extra/CONNMARK.patch...
   Placed new Config.in line
   Placed new Config.in line
   Placed new Config.in line
   Placed new Configure.help entry
   Placed new Makefile line
   Placed new Makefile line
Failed to patch copy of /usr/src/linux
TEST FAILED: patch NOT applied.

[Press enter to continue]


Im using from source

iptables 1.2.7a
patch-o-magic 20021008
have tried with newer cvs image patch-o-magic and did'nt even work
kernel 2.4.18-19 both have the same problem.

Does anybody know if theres a workaround for this thingie?.. or am i just
lost in my dreams until a new release come? Is there a way i can check what
the error is?

- SilverWolf

             reply	other threads:[~2002-11-09 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09 11:43 Matias Bjørling [this message]
2002-11-12 10:11 ` CONNMARK Patching Problem Martin Josefsson

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='005a01c287e5$2d0862a0$0200000a@parseerror.dk' \
    --to=mb@ncparty.dk \
    --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.