From owner-freebsd-doc  Mon Jan 29 17:49:19 2001
Delivered-To: freebsd-doc@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
	by hub.freebsd.org (Postfix) with ESMTP id 9BD3F37B402
	for <doc@FreeBSD.org>; Mon, 29 Jan 2001 17:49:01 -0800 (PST)
Received: by bazooka.unixfreak.org (Postfix, from userid 1000)
	id 3C1BD3E02; Mon, 29 Jan 2001 17:49:01 -0800 (PST)
Received: from unixfreak.org (localhost [127.0.0.1])
	by bazooka.unixfreak.org (Postfix) with ESMTP
	id 354183C10B; Mon, 29 Jan 2001 17:49:01 -0800 (PST)
To: Kris Kennaway <kris@obsecurity.org>
Cc: doc@FreeBSD.org
Subject: Re: Problem with top in 4.2-RELEASE? 
In-Reply-To: Message from Kris Kennaway <kris@obsecurity.org> 
   of "Mon, 29 Jan 2001 12:12:27 PST." <20010129121227.A26431@xor.obsecurity.org> 
Date: Mon, 29 Jan 2001 17:48:56 -0800
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010130014901.3C1BD3E02@bazooka.unixfreak.org>
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

[ Dropped -chat ]

> > Ion:/etc# top
> > top: nlist failed
> 
> [snip answer]
>
> Someone REALLY needs to add the above to the FAQ. Doc guys?

How's this?  If the markup bothers you, you can find the rendered
version here:

http://www.unixfreak.org/~dima/home/freebsd/data/FAQ/troubleshoot.html#NLIST-FAILED

					Dima Dorfman
					dima@unixfreak.org


Index: book.sgml
===================================================================
RCS file: /st/src/FreeBSD/doc/en_US.ISO_8859-1/books/faq/book.sgml,v
retrieving revision 1.140
diff -u -r1.140 book.sgml
--- book.sgml	2001/01/18 01:14:24	1.140
+++ book.sgml	2001/01/30 01:34:16
@@ -4166,6 +4166,41 @@
 
         </answer>
       </qandaentry>
+
+      <qandaentry>
+        <question id="nlist-failed">
+          <para>I get the error <literal>nlist failed</literal> when running,
+            for example, <command>top</command> or
+            <command>systat</command>.</para>
+        </question>
+
+        <answer>
+          <para>The problem is that the application you are trying to run is
+            looking for a specific kernel symbol, but, for whatever reason,
+            cannot find it; this error stems from one of two problems:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>Your kernel and userland are not synchronized (i.e., you
+                built a new kernel but did not do an installworld, or vice
+                versa), and thus the symbol table is different from what the
+                user application thinks it is.  If this is the case, simply
+                complete the upgrade process (see
+                <filename>/usr/src/UPDATING</filename> for the correct
+                sequence).</para>
+            </listitem>
+
+            <listitem>
+              <para>You are not using <command>/boot/loader</command> to load
+                your kernel, but doing it directly from boot0 (see
+                &man.boot.8;).  While there is nothing wrong with bypassing
+                <command>/boot/loader</command>, it generally does a better
+                job of making the kernel symbols available to user
+                applications.</para>
+            </listitem>
+          </itemizedlist>
+        </answer>
+      </qandaentry>
     </qandaset>
   </chapter>
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message