From owner-freebsd-questions@FreeBSD.ORG Thu Nov 6 15:03:39 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D50616A4CE for ; Thu, 6 Nov 2003 15:03:39 -0800 (PST) Received: from be-well.no-ip.com (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87ECA43FE3 for ; Thu, 6 Nov 2003 15:03:38 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.no-ip.com (Postfix, from userid 1147) id C7D183B09; Thu, 6 Nov 2003 18:03:35 -0500 (EST) Sender: lowell@be-well.ilk.org To: freebsd-questions@freebsd.org References: <15502.216.237.145.172.1068153138.squirrel@mail02.oldskool.com> <20031107080233.0900bd64.tim@spyderweb.com.au> From: Lowell Gilbert Date: 06 Nov 2003 18:03:35 -0500 In-Reply-To: <20031107080233.0900bd64.tim@spyderweb.com.au> Message-ID: <44sml1cd6g.fsf@be-well.ilk.org> Lines: 61 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: make dev problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Nov 2003 23:03:39 -0000 Tim Aslat writes: > In the immortal words of "Jason Burris" ... > > I need to compile a kernel with IPFW on a remote machine running > > FreeBSD4.7. I followed the steps listed at: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html > > Following the handbook isn't a bad start. It's nice to see someone actually do it for a change. > > In my COMPUTERNAME config file I've add the following three lines to > > the end for IPFW: > > > > options IPFIREWALL > > options IPFIREWALL_VERBOSE > > options IPFIREWALL_DEFAULT_TO_ACCEPT > > > > And I changed this line, which I read was necessary: > > > > ident COMPUTERNAME > > Not bad, but a more secure way would be to default to deny rather than > accept, but that's personal preference. In this case, where the machine is remote and you could lock yourself out, it's probably better to default to accept instead. Eventually, there will be a firewall rule denying unmatched packets, and even then you have to be careful about backing out the ruleset automatically if you lock yourself out. > > I'm able to run: > > > > /usr/sbin/config COMPUTERNAME > > cd ../../compile/COMPUTERNAME > > > > When I run > > > > make depend > > > > Everything runs fine until it dies with the error: > > > > make: don't know how to make iconv.h. > > Stop*** Error code 2 > > Stop in /usr/src/sys/modules.*** > > Error code 1 > > > > I've checked and this file is in my /usr/src/sys directory.What am I > > doing wrong? Do I even need this header to be compiled intothe > > kernel? > > You might want to try the "newer" method of building a kernel. > > cd /usr/src > make buildkernel KERNCONF=COMPUTERNAME > > make installkernel KERNCONF=COMPUTERNAME I don't think that will be any better. Either way, he needs to have sources that match his system, and the "old" way will work fine when that is the case.