All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex-cmaem7PIVQQM4YKboWzA4l6hYfS7NtTn@public.gmane.org>
To: netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.org
Subject: Re: newbie struggling with p-o-m in kernel 2.6
Date: Sun, 14 Mar 2004 06:32:35 -0500	[thread overview]
Message-ID: <c31fsj$l7s$1@sea.gmane.org> (raw)
In-Reply-To: MPG.1abbd219144e52d99896a5@localhost

Okay, I've figured out a couple of things.

> - I grabbed patch-o-matic-ng-20040302, and tried it.  But it won't apply
> the condition and time patches, because both of them are marked 'linux
> < 2.6.0'.

By deleting the line 'Requires: linux < 2.6.0' from the info files for these
two parches, I got pom-ng to apply both of them to kernel 2.6.3 with
complaint.  The kernel then built with no trouble, although the option help
texts weren't available in 'make xconfig'.  However I haven't tested the
modules yet.  But it seems that at least these two extensions are close to
ready for kernel 2.6.
 
> - Even though I try to run runme in batch mode, it always asks where my
> iptables source code is.  Looking through the script, there doesn't seem
> to be an environment variable to set for that.

Looking through the runme script again, I figured out that we have a new
option for specifying the kernel and iptables source paths:

--path $KERNEL_DIR:$IPTABLES_DIR

Of course this needs to be documented for the user.  And, I should be able
to set an environment variable IPTABLES_DIR just as I do KERNEL_DIR, in
order to avoid typing the directories on the command line each time.




      parent reply	other threads:[~2004-03-14 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 18:57 newbie struggling with p-o-m in kernel 2.6 Andrew Schulman
2004-03-13  8:39 ` RRuegner
2004-03-14 11:32 ` Andrew Schulman [this message]

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='c31fsj$l7s$1@sea.gmane.org' \
    --to=andrex-cmaem7pivqqm4ykbowza4l6hyfs7nttn@public.gmane.org \
    --cc=netfilter-wool9L35kiczKOhml7GhPkB+6BGkLq7r@public.gmane.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.