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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
