Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jack Bowling <jbinpg@shaw.ca>
To: netfilter@lists.samba.org
Subject: Re: Help with invalid argument
Date: Sat, 06 Jul 2002 11:31:37 -0700	[thread overview]
Message-ID: <0GYU00921BGS9X@l-daemon> (raw)
In-Reply-To: <EPEHIDPIPEBFNAHLCHPGCEMGCEAA.dennis@core-enterprises.com>

** Reply to message from Dennis Cardinale <dennis@core-enterprises.com> on Sat, 06 Jul 2002 12:44:56 -0400


> what happens if I boot the old kernel?
> 
> -----Original Message-----
> From: netfilter-admin@lists.samba.org
> [mailto:netfilter-admin@lists.samba.org]On Behalf Of Jack Bowling
> Sent: Saturday, July 06, 2002 12:38 PM
> To: netfilter@lists.samba.org
> Subject: Re: Help with invalid argument
> 
> 
> ** Reply to message from Dennis Cardinale <dennis@core-enterprises.com> on
> Sat, 06 Jul 2002 12:31:21 -0400
> 
> 
> > OK...solved my own problem.
> >
> > userspace/make install all
> >
> > does not copy the new iptables binaries to the /sbin directory.
> >
> > Is there a script to do this?  Can I do it manually? Is there a way to do
> it
> > so that the binaries used are compatible with the chosen kernel at boot
> > time?
> 
> Just edit this section of the Makefile in your iptables source top directory
> to the following:
> 
> #PREFIX:=/usr/local
> LIBDIR:=/lib
> BINDIR:=/sbin
> MANDIR:=/usr/share/man
> INCDIR:=/usr/include
> 
> before you do the make and make install.


The above Makefile only controls where the userspace part of iptables goes during the make install. The netfilter kernel modules are added to the kernel source when you do the "make most-of-pom", etc. Then you have to compile your kernel source again. If you have already compiled the kernel source using the same iptables code then you just have to run the make install again (with the edited prefixes) to put the userspace stuff in the right place. It may be an idea to go into the /usr/local directory and clean out all the stuff that was placed in there by the previous make install just to avoid possible clashes.

jb


  reply	other threads:[~2002-07-06 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06  2:03 Help with invalid argument Dennis Cardinale
2002-07-06 16:31 ` Dennis Cardinale
2002-07-06 16:38   ` Jack Bowling
2002-07-06 16:44     ` Dennis Cardinale
2002-07-06 18:31       ` Jack Bowling [this message]
2002-07-06 19:20         ` Dennis Cardinale
2002-07-06 19:57           ` Jack Bowling

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=0GYU00921BGS9X@l-daemon \
    --to=jbinpg@shaw.ca \
    --cc=netfilter@lists.samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox