From owner-freebsd-questions@FreeBSD.ORG Mon Apr 7 16:08:20 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F04937B401 for ; Mon, 7 Apr 2003 16:08:20 -0700 (PDT) Received: from blueyonder.co.uk (pcow058o.blueyonder.co.uk [195.188.53.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 173EB43FD7 for ; Mon, 7 Apr 2003 16:08:19 -0700 (PDT) (envelope-from jfm@blueyonder.co.uk) Received: from lexx ([62.31.198.203]) by blueyonder.co.uk with Microsoft SMTPSVC(5.5.1877.757.75); Tue, 8 Apr 2003 00:08:17 +0100 From: John Murphy To: questions@FreeBSD.ORG Date: Tue, 08 Apr 2003 00:08:17 +0100 Organization: poor Message-ID: References: <20030407122013.92408.qmail@mx.tele-kom.ru> In-Reply-To: <20030407122013.92408.qmail@mx.tele-kom.ru> X-Mailer: Forte Agent 1.9/32.560 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Re: 4.8 ipfilter ruleset compatibility question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jfm@blueyonder.co.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2003 23:08:20 -0000 DoubleF wrote: >> > > Not sure if it's related but I've just tried top again: >> > > wall# top >> > > top: nlist failed >> >=20 >> > Things like this usually happen if your kernel is out of sync with = your >> > userland. "ps" is probably also broken if you're out of sync. >> > - jim >>=20 >> IMHO, the "/boot/loader" and "boot[012]" are out of sync with the >> kernel. When I updated 4.4 to 4.7, it was the same thing. >> (Re?)installing these boot tools fixed it. > >Hope this doesn't sound like a stupid tip: if during boot you see the >string like > /kernel: text=3D..., data=3D..., ... >with "syms=3D..." in it, the loader is sane. Otherwise - punish him;) Useful, I'll look out for that. The box is headless though so I don't see that stage very often. I was probably running kernel.GENERIC at the time when top failed (with rc.conf trying to do ipfilter things), and I'd loaded it by interrupting the countdown. But absolutely nothing other = than configuration files came from the old installation, so the world (as I understand it) couldn't have been out of sync. Thanks John.