From owner-freebsd-current@FreeBSD.ORG Tue Jun 10 03:12:49 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 384A237B401 for ; Tue, 10 Jun 2003 03:12:49 -0700 (PDT) Received: from mailspool.ops.uunet.co.za (mailspool.ops.uunet.co.za [196.7.0.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE6E743FE1 for ; Tue, 10 Jun 2003 03:12:47 -0700 (PDT) (envelope-from ianf@mci.com) Received: from copernicus.so.cpt1.za.uu.net ([196.30.72.32]) by mailspool.ops.uunet.co.za with esmtp (Exim 3.36 #1) id 19Pg6z-0002rm-00; Tue, 10 Jun 2003 12:12:17 +0200 Received: from localhost ([127.0.0.1] helo=mci.com) by copernicus.so.cpt1.za.uu.net with esmtp (Exim 3.36 #1) id 19Pg6s-0000fF-00; Tue, 10 Jun 2003 12:12:10 +0200 To: "Daniel C. Sobral" In-reply-to: Your message of "Mon, 09 Jun 2003 17:32:55 -0300." <3EE4EEF7.1010208@tcoip.com.br> References: <3EE4EEF7.1010208@tcoip.com.br> From: Ian Freislich X-image-url: http://www.digs.iafrica.com/gallery/ian-small.gif X-BOFH: true X-LART: Depleted uranium X-No-Junk-Mail: I do not want to get *any* junk mail. You have been deleted Date: Tue, 10 Jun 2003 12:12:10 +0200 Message-ID: <2556.1055239930@mci.com> Sender: ianf@mci.com 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 10:12:49 -0000 "Daniel C. Sobral" wrote: > John Stockdale wrote: > > Hey everyone, > > > > I just cvsup'd my src today and was going to buildworld later tonight > > but when I installed the newly built kernel with IPFIREWALL etc. and > > rebooted, ipfw fell over, specifically, even after ipfw firewall enable, > > an ipfw show resulted in a core dump. If its useful, I can post the ipfw > > core dump. > > > > Any ideas why this is? > > Probably because the ABI between ipfw(8) and it's kernel counterpart has > changed. Since you failed to follow the safe path of upgrade > (mergemaster -p, builworld, buildkernel, installkernel, reboot -s (fall > back in case of problems), mount fs and installkernel, mergemaster), > this sort of things can happen. Alas make buildworld fails for the past few days: ===> usr.sbin/config In file included from config.c:1: /usr/include/stdlib.h:102: conflicting types for `restrict' /usr/include/stdlib.h:102: previous declaration of `restrict' /usr/include/stdlib.h:102: warning: redundant redeclaration of `restrict' in same scope /usr/include/stdlib.h:102: warning: previous declaration of `restrict' /usr/include/stdlib.h:103: conflicting types for `restrict' (and also stdio.h, string.h, sys/types.h, select.h) Someone posted a link to the failure that I get, so I'll crib: http://www.0xfce3.net/error.txt > Granted, that rather laborious process is usually unnecessary. I, > myself, often use only buildworld, kernel, installworld, mergemaster and > then reboot. And, of course, I'm fully prepared to take Murphy's Revenge > upon my shoulder if these simple steps fail to yield a working system (a > broken kernel, for instance, with a new world incompatible with the > previous kernel). > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought > to fix it. I tried that as well, but the new binary also dumps core, but works well with previous versions of the firewall. Even back as far as my kernel.working from May 7 2003.