All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Samuel Díaz García" <samueldg@arcoscom.com>
To: Jorge Davila <davila@cablenet.com.ni>
Cc: netfilter@lists.netfilter.org
Subject: Re: pom-ng "condition" for 2.6 kernels
Date: Tue, 03 Jan 2006 15:48:00 +0100	[thread overview]
Message-ID: <43BA8EA0.5060907@arcoscom.com> (raw)
In-Reply-To: <1136298300.2565.10.camel@davila.nicaraguaopensource.com>

Jorge, I don't know if you stand me, but the problem isn't if I know how 
to use patch-o-matic.

The problem is a bug in patch-o-matic (or mistake) that don't allow to 
use "condition" patch with 2.6.x kernels.

I explain in the message you reply.

Regards

Jorge Davila escribió:

> well, you can do the next to avoid write some vars in the ./runme
> command:
> 
> export KERNEL_DIR=/path/to/kernel/source/code
> export IPTABLES_DIR=/path/to/iptables/source/code
> 
> in the patches source code, run:
> 
> ./runme <pending|base|extras>
> 
> I don't exactly what option will show you the patch that you want apply.
> 
> Jorge.
> 
> El mar, 03-01-2006 a las 15:17 +0100, Samuel Díaz García escribió:
> 
>>Fine, I know how to apply pom without problems.
>>
>>The problem is that applying over a 2.6.14.5 kernel (2.6.x kernels) the 
>>"condition" patch isn't showed for the apply.
>>
>>"Kovacs Krisztian" (hidden_#arroba#_balabit.hu) sent to me the patch to 
>>apply over an 2.6.14.5 kernel and appears to be working fine (at least 
>>applied, compiled and installed with the new compiled kernel).
>>
>>I had tried to found the problem, and I think that the "condition" isn't 
>>ported into 2.6.x kernels because a "linux-2.6" directory doesn't exist 
>>into the "patchlets/condition", and that (I think) is because 
>>"condition" isn't showed while "./runme extra" is running.
>>
>>I want to know if really "condition" is included for 2.6 kernels into 
>>pom-ng and why is failing the "./runme".
>>
>>Sorry for my poor english.
>>
>>Regards.
>>
>>Jorge Davila escribió:
>>
>>
>>>In the patches source code directory:
>>>
>>>KERNEL_DIR=/the/path/to/kernel-2.6.14/source/code/directory
>>>IPTABLES_DIR=/the/path/to/iptables/source/code/directory ./runme
>>><pending|base|extras>
>>>
>>>Of course, you need the source code for your kernel and for iptables.
>>>
>>>Jorge.
>>>
>>>El dom, 01-01-2006 a las 23:06 +0100, Samuel Díaz García escribió:
>>>
>>>
>>>>Is there any way to apply "condition" patch into 2.6.14 kernel?
>>>>
>>>>I can see "linux" directory into "patchlets/condition" but not a 
>>>>"linux-2.6" directory.
>>>>
>>>>Any help about it?
>>>>
>>>>Thanks
>>>>
>>

-- 
    Samuel Díaz García
     Director Gerente
ArcosCom Wireless, S.L.L.

CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz

http://www.arcoscom.com

mailto:samueldg@arcoscom.com
msn: samueldg@arcoscom.com

Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax:   956 70 34 83


  reply	other threads:[~2006-01-03 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-01 22:06 pom-ng "condition" for 2.6 kernels Samuel Díaz García
2006-01-02 17:53 ` Jorge Davila
2006-01-03 14:17   ` Samuel Díaz García
2006-01-03 14:25     ` Jorge Davila
2006-01-03 14:48       ` Samuel Díaz García [this message]
2006-01-03 15:03         ` KOVACS Krisztian
2006-01-04 11:26           ` Pedro Drimel Neto

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=43BA8EA0.5060907@arcoscom.com \
    --to=samueldg@arcoscom.com \
    --cc=davila@cablenet.com.ni \
    --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.