From: Aleksander Kamenik <aleksander@krediidiinfo.ee>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ipp2p segmentation fault
Date: Sun, 07 Oct 2007 11:08:19 +0000 [thread overview]
Message-ID: <4708BE23.5010404@krediidiinfo.ee> (raw)
In-Reply-To: <470722AD.2080303@ddihealth.com>
Jim Barber wrote:
> So it'll get the latest at the time, which on Sep 26th was 0.8.1_rc1, if
> I had waited a day or two 0.8.2 would have been out.
0.8.2 was released Sep 26 _2006_. More than a year ago.
>
> I'll try again using the newer version.
So how did that go?
The reason for not using pom is the simplicity of the manual install.
After compiling you get two files, the kernel module and the iptables
module. Copy them into the correct places, run depmod -a for the kernel
module and you're ready to go. Easy to see where you've gone wrong if
there's a problem.
Also, why did you install your own version of iptables? Does pom require it?
The problem probably is that the ipp2p module for iptables was either
compiled for the wrong version or you're trying to use it with the wrong
version of iptables.
Regards,
--
Aleksander Kamenik
system administrator
+372 6659 649
aleksander@krediidiinfo.ee
Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-10-07 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 5:52 [LARTC] ipp2p segmentation fault Jim Barber
2007-10-06 12:25 ` Aleksander Kamenik
2007-10-06 12:51 ` Mario Antonio Garcia
2007-10-06 23:42 ` Jim Barber
2007-10-07 0:47 ` Jim Barber
2007-10-07 11:08 ` Aleksander Kamenik [this message]
2007-10-07 13:36 ` Jim Barber
2007-10-08 9:17 ` ArcosCom Linux User
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=4708BE23.5010404@krediidiinfo.ee \
--to=aleksander@krediidiinfo.ee \
--cc=lartc@vger.kernel.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.