On Friday 09 November 2001 02:12 am, you wrote: if you included options IPFIREWALL in your kernel, you don't need to kldload the module, and it may mess some things up if you do try to kldload it.
> This morning I've cvsuped to STABLE and put 'options IPFIREWALL' into my > kernel configuration file. After installing all I try to 'kldload ipfw' > which complains that ipfw module is already in kernel, but kldstat reports > that module is being loaded! Then I've decided to kldunload it.... Kernel > panic .... reboot! > > It is regular to kernel crash if ipfw is loaded as module, but why when it > was build into kernel? In that case it would be good kldload/kldunload to > exit! Why kldload loads module in case that it is compiled in kernel? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
