From owner-freebsd-current Sat Jan 9 00:07:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25634 for freebsd-current-outgoing; Sat, 9 Jan 1999 00:07:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25625 for ; Sat, 9 Jan 1999 00:07:51 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.2/8.9.2) with ESMTP id IAA17614; Sat, 9 Jan 1999 08:07:11 GMT Message-ID: <36970E00.8215AE29@tdx.co.uk> Date: Sat, 09 Jan 1999 08:06:24 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: John Polstra CC: current@FreeBSD.ORG Subject: Re: dmesg: namelist: msgbufp not found? References: <199901090628.WAA45726@vashon.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > In article <3695D539.FCDBE542@tdx.co.uk>, > Karl Pielorz wrote: > > > > I only have 2 problems with it, the first of which is when I run dmesg I get: > > > > caladan# dmesg > > dmesg: namelist: msgbufp not found > > Hmm ... it works for me. Did you strip your kernel, perhaps? "file > /kernel" will tell you whether it's stripped. Yes, I stripped it... I'm sure I'd already posted a reply to myself to say "I found the problem"... :) Is there a way to strip it, and not break it? - I used to use "strip -d -aout kernel", which doesn't work anymore :( (the elves don't like it)... Although I'm not short of memory, running a 7Mb kernel can't b too healthy... :) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message