Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 08 Apr 2003 00:08:17 +0100
From:      John Murphy <jfm@blueyonder.co.uk>
To:        questions@FreeBSD.ORG
Subject:   Re: 4.8 ipfilter ruleset compatibility question
Message-ID:  <n3u39vo426brghnv4rao87goan07otr97i@4ax.com>
In-Reply-To: <20030407122013.92408.qmail@mx.tele-kom.ru>
References:  <20030407122013.92408.qmail@mx.tele-kom.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

DoubleF <doublef@tele-kom.ru> wrote:

>> > > Not sure if it's related but I've just tried top again:
>> > > wall# top
>> > > top: nlist failed
>> > 
>> > 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
>> 
>> 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=..., data=..., ...
>with "syms=..." 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?n3u39vo426brghnv4rao87goan07otr97i>