Skip to contentSkip to conversation

conntrack-acct "workaround" for 2.6.9+

PATCH In review Jonas Berlin 2 participants 2 messages Feb 17, 2005 – Feb 19, 2005 netfilter

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 conntrack-acct "workaround" for 2.6.9+

patch-o-matic-ng fails to detect that conntrack-acct is already applied (I don't know how it does the detection) and thus fails when trying to apply it.

However, if an empty file called linux-2.6.9.patch is placed in the conntrack-acct/ directory, everything works just fine.

I noticed this problem when I was trying to patch connbytes into the kernel (which depends on conntrack-acct). After adding the empty patch file, connbytes also went in just fine.

So unless there's a better way of fixing it in the patch-o-matic-ng detection code, maybe someone with commit rights just create an empty conntrack-acct/linux-2.6.9.patch file :)

(I verified that the original patch worked until 2.6.8 ; hence my choice of 2.6.9)

Signature · 1 line
- xkr47
#1 lore raw
Quoted 6 lines · Jonas Berlin

patch-o-matic-ng fails to detect that conntrack-acct is already applied (I don't know how it does the detection) and thus fails when trying to apply it.

However, if an empty file called linux-2.6.9.patch is placed in the conntrack-acct/ directory, everything works just fine.

conntrack-acct shouldn't be in patch-o-matic in the first place. As we decided (after conntrack-acct was in) only new features / new modules should be part of patch-o-matic.

In my current post-2.6.11 patch-o-matic branch in svn, I'm also getting rid of all those pathes (especially patch-o-matic-ng/conntrack-*)

Signature · 5 lines
- Harald Welte <[email protected]>                 http://netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie