From owner-freebsd-current@FreeBSD.ORG Tue Jun 10 05:58:07 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B27337B401 for ; Tue, 10 Jun 2003 05:58:07 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9646343FD7 for ; Tue, 10 Jun 2003 05:58:06 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h5ACw6AQ091077; Tue, 10 Jun 2003 08:58:06 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h5ACw5S9091074; Tue, 10 Jun 2003 08:58:06 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 10 Jun 2003 08:58:05 -0400 (EDT) From: Andre Guibert de Bruet To: Ian Freislich In-Reply-To: <5981.1055249140@mci.com> Message-ID: <20030610085620.X56112@alpha.siliconlandmark.com> References: <20030610083242.S56112@alpha.siliconlandmark.com> <5981.1055249140@mci.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: New Kernel Breaks IPFW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 12:58:07 -0000 On Tue, 10 Jun 2003, Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > > > The new ipfw binary will work with an up-to-date kernel. What you need to > > do is boot this new kernel and only then try out the new ipfw binary. > > That doesn't really explain why the new ipfw binary core dumped > with the new kernel, but worked fine with old kernels. > > Now that I've removed BDECFLAGS, it seems that my buildworld will > succeed and whatever it was that was broken that ipfw linked in > (statically) will hopefully be fixed and all will be good in my > land of -CURRENT, for the moment that is. With CFLAGS of -O -pipe and a conservative value of CPUTYPE (ie not p4), everything should be okay: It works here(tm)! ;-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >