From: Pollywog <linux@shadypond.com>
To: netfilter@lists.netfilter.org
Subject: Re: Small doubt from a newbie :)
Date: Fri, 10 Nov 2006 18:09:45 +0000 [thread overview]
Message-ID: <200611101809.45803.linux@shadypond.com> (raw)
In-Reply-To: <45543A8E.7070606@gmail.com>
On Friday 10 November 2006 08:38, utteerna wrote:
> Here's steps i followed and error details. Please let me know if i
> missed something
Are you running Debian or a Debian derivative?
>
> 1)Downloaded linux-2.6.18.2 and put it in /usr/src dir and untarred it
> 2)Downloaded iptables-1.3.6 and put it in /usr/src dir and untarred it
> 3)Downloaded patch-o-matic-ng-20061108.tar and put it in /usr/src dir
> and untarred it
Since you are installing patch-o-matic, I assume you are going to compile
ipsets... is that why you need patch-o-matic? I just did this recently
because I use ipsets with Shorewall.
I am also not sure why you did not install the iptables package that comes
with your distribution, unless it is because you need a newer version for
ipsets.
I would configure the kernel first, and least through the 'make config' part
even if you don't compile it. If you do that and then apply the patches, all
you need to do is run 'make oldconfig' if you are running Linux. Then you
know that you will need to say "Y" to the new options.
After you have patched the kernel and added the new options as I mentioned
above, you can compile the kernel. Also, if you are running Debian or a
derivative of Debian, I can explain how to compile a kernel the Debian way.
I have not had to do it "the old way" in a long time.
8)
prev parent reply other threads:[~2006-11-10 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 8:34 Small doubt from a newbie :) utteerna
2006-11-07 9:25 ` Rob Sterenborg
2006-11-07 11:26 ` utteerna
2006-11-07 12:19 ` Rob Sterenborg
2006-11-07 9:36 ` Marco Berizzi
2006-11-08 11:53 ` utteerna
2006-11-09 10:27 ` Marco Berizzi
2006-11-10 8:38 ` utteerna
2006-11-10 10:04 ` Marco Berizzi
2006-11-14 4:22 ` utteerna
2006-11-10 18:09 ` Pollywog [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=200611101809.45803.linux@shadypond.com \
--to=linux@shadypond.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.