Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Emanoil Kotsev <emanuel@abc.at>
To: netfilter@lists.netfilter.org
Subject: compiling iptables support for other machine
Date: Sat, 03 May 2003 13:29:01 +0200	[thread overview]
Message-ID: <3EB3A7FD.22A17A1@abc.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

Hi, folks,

I might be wrong looking for help in this forum but as it is related to
the topic I hope someone can give me a usefull advice or an idea where
I can find related information to solve the following problem:
=====
I am trying to compile a new kernel on my machine (MA) for anathor
machine (MB) that I am using as firewall, where I need extended iptables
support.

MB is very slow and does not have enough diskspace, so I can not install
compilers or headers there.
Tehre is enough space for a new kernel though.

What I was trying ot do is to compile the kernel on MA and to install it
after I nfs-mount the linux-directory from MA to MB.
Unfortunately a developers environment on MB is missing and I got
following error after i do
make install

make: *** No rule to make target
`/usr/src/kernel-source-2.4.20/include/asm/param.h', needed by
`/usr/src/kernel-source-2.4.20/include/linux/sched.h'.  Stop.

Unfortunately on MA everything is compiling fine - where is the problem
what do I need for the asm/param.h

Is it enough to compile on MA and to copy the relevant stuff eg. vmlinuz
+ modules to MB

thanks a lot

--
+ Emanoil Kotsev - - - - -+
+ E-Mail: emanuel@t2u.com +



[-- Attachment #2: Type: text/html, Size: 1380 bytes --]

             reply	other threads:[~2003-05-03 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-03 11:29 Emanoil Kotsev [this message]
2003-05-04  4:39 ` compiling iptables support for other machine Julian Gomez

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=3EB3A7FD.22A17A1@abc.at \
    --to=emanuel@abc.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox