Date: Tue, 13 Aug 2002 21:53:37 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: current@FreeBSD.ORG Subject: Re: Weirdness trying -STABLE -> -CURRENT Message-ID: <20020813195337.GE1105@fonix.adamsfamily.xx> In-Reply-To: <3D596170.6030107@myrealbox.com> References: <20020811194119.GA897@fonix.adamsfamily.xx> <200208130004.g7D04e2T003783@bunrab.catwhisker.org> <20020813163333.GD1105@fonix.adamsfamily.xx> <3D596170.6030107@myrealbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 13, 2002 at 01:43:44PM -0600, Kyle Butt wrote: > Szilveszter Adam wrote: > >(At this point you are running on the -CURRENT kernel but with the old > >userland: be aware of this because things like ipfw will now stop > >working until you are back in sync!) > > > The trick here is that a new loader isn't installed yet. the old kernel > lives in /kernel and the new one in /boot/kernel/kernel you have to be > sure and boot the new one. make -k installworld accomplishes the same > thing (By installing a new loader) I was not merely thinking of this. For ipfw to work, the kernel and the /sbin/ipfw binary have to match, or else adding or otherwise manipulating rules will likely fail. This will either result in a wide-open firewall or a tightly closed one, depending on the kernel config. This happens even when the ipfw support is not loaded from a module. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020813195337.GE1105>