From owner-freebsd-current Tue Aug 13 12:53:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A946237B400 for ; Tue, 13 Aug 2002 12:53:46 -0700 (PDT) Received: from mx1.datanet.hu (mx1.datanet.hu [194.149.13.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2216543E3B for ; Tue, 13 Aug 2002 12:53:46 -0700 (PDT) (envelope-from sziszi@bsd.hu) Received: from fonix.adamsfamily.xx (nilus-1647.adsl.datanet.hu [195.56.94.123]) by mx1.datanet.hu (DataNet) with ESMTP id 3C9EF26A1D5 for ; Tue, 13 Aug 2002 21:53:39 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.5/8.12.5) with ESMTP id g7DJrc8g009861 for ; Tue, 13 Aug 2002 21:53:38 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.5/8.12.5/Submit) id g7DJrbLl009860 for current@FreeBSD.ORG; Tue, 13 Aug 2002 21:53:38 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Tue, 13 Aug 2002 21:53:37 +0200 From: Szilveszter Adam To: current@FreeBSD.ORG Subject: Re: Weirdness trying -STABLE -> -CURRENT Message-ID: <20020813195337.GE1105@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.ORG References: <20020811194119.GA897@fonix.adamsfamily.xx> <200208130004.g7D04e2T003783@bunrab.catwhisker.org> <20020813163333.GD1105@fonix.adamsfamily.xx> <3D596170.6030107@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D596170.6030107@myrealbox.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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