Date: Sun, 30 Jul 2000 18:50:31 -0400 From: Bill Fumerola <billf@chimesnet.com> To: Arcady Genkin <a.genkin@utoronto.ca> Cc: Kris Kennaway <kris@FreeBSD.org>, FreeBSD-Stable <stable@freebsd.org> Subject: Re: ipfw core dumped on 4.1-S Message-ID: <20000730185031.V5021@jade.chc-chimes.com> In-Reply-To: <87snsr5k11.fsf@tea.thpoon.com>; from a.genkin@utoronto.ca on Sun, Jul 30, 2000 at 06:29:46PM -0400 References: <Pine.BSF.4.21.0007301518140.6951-100000@freefall.freebsd.org> <87snsr5k11.fsf@tea.thpoon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 30, 2000 at 06:29:46PM -0400, Arcady Genkin wrote:
> > This sometimes happens if your ipfw(8) binary is out of sync with the
> > kernel it's running on. You did rebuild the kernel with the same sources
> > (not e.g. after doing a cvsup in the middle), of course?
>
> Yeah, I did everything as the doctor prescribed (make buildworld, make
> buildkernel, installkernel, installworld). ;^)
>
> However, I just recompiled everything in /sbin just in case, and
> recompiled my kernel. Before I isolated the command from
> /etc/security which caused the core dump; all works fine now.
That means that you really didn't have a ipfw(8) that was in sync
with your ipfw(4) in your kernel.
here's what I'm 99% sure happened:
make installworld KERNEL=FOO installs /FOO and not /kernel like
everyone who has ever used FreeBSD expects it to. you booted your
old /kernel, even though /FOO was right there ready to be used.
you probably just recompiled the kernel in place (like we traditionally
used to) and then did a make install which (as POLA would tell us)
installs /kernel.
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
billf@chimesnet.com / billf@FreeBSD.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000730185031.V5021>