From owner-freebsd-hackers Thu Oct 10 22:21:10 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7688937B401 for ; Thu, 10 Oct 2002 22:21:09 -0700 (PDT) Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CE6743EAF for ; Thu, 10 Oct 2002 22:21:09 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0520.cvx40-bradley.dialup.earthlink.net ([216.244.44.10] helo=mindspring.com) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17zsEP-00079Q-00; Thu, 10 Oct 2002 22:21:02 -0700 Message-ID: <3DA65F77.C812618C@mindspring.com> Date: Thu, 10 Oct 2002 22:19:51 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bill Fumerola Cc: abe , hackers@freebsd.org Subject: Re: fatal trap 12 kernel panic References: <20021010212954.GA67855@dipole.informationwave.net> <3DA5F3BC.CD0154CF@mindspring.com> <20021010214518.GB71656@dipole.informationwave.net> <3DA5FCD2.B23CD912@mindspring.com> <20021010222545.GA82461@dipole.informationwave.net> <3DA60447.4C66C85@mindspring.com> <20021010232416.GA97757@dipole.informationwave.net> <3DA6332C.CDC30B95@mindspring.com> <20021011030207.GN80284@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Thu, Oct 10, 2002 at 07:10:52PM -0700, Terry Lambert wrote: > > Not to be emphatic, or anything, but IPFW has to be static. There > > is voodoo you can use to make it know about loaded modules, but I'll > > be damned if I know what it is (again, I refer you to the handbook). > > 8-). > > nope. ipfw doesn't have to be static. ipfw+ipdivert has to be static. > up until a while ago, ipfw+dummynet and ipfw+bridge had to be static, > but that was fixed and MFC'd. ipfw by itself (which includes the dynamic > rules) can be static or kldload'd. It has to be static to be abe to get source code from a dump address inside the code, which varies, when it's a module, so you can't decode it from the kernel and the module itself, without knowing where the module loaded. It's doesn't "have to be static" for operational reasons; that's not what I'm claiming. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message