From owner-freebsd-stable Tue Dec 2 13:49:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA07257 for stable-outgoing; Tue, 2 Dec 1997 13:49:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA07251 for ; Tue, 2 Dec 1997 13:49:06 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA16339; Wed, 3 Dec 1997 08:48:59 +1100 (EST) Date: Wed, 3 Dec 1997 08:48:58 +1100 (EST) From: "Daniel O'Callaghan" To: Dan Jacobowitz cc: freebsd-stable@FreeBSD.ORG Subject: Re: ipfw between kernel versions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Dec 1997, Dan Jacobowitz wrote: > > 2.2.5 ipfw will not work with 2.2.2-RELEASE kernels, but will work with > > 2.2.2-STABLE after August 21st. > > What about /lkm/ipfw_mod.o? Should I upgrade the lkms immediately with > kernel or wait until I make world? Does 2.2.5 ipfw use the lkm? > > It strikes me as a little odd that the lkms are not included in the kernel > tree; wouldn't it make more sense to have perhaps /sys/lkm? I'm sure > there's a good reason why not, but I don't see what it is. If you build a kernel with IPFIREWALL, the lkm is not used. In 2.2.5 rc.conf and rc.network were changed to so that the lkm will be loaded if required. Since lkms are loaded early in the boot process, they need to be available before /usr and other filesystems are mounted, hence /lkm needs to be in the root partition. Danny /* Daniel O'Callaghan */ /* HiLink Internet danny@hilink.com.au */ /* FreeBSD - works hard, plays hard... danny@freebsd.org */