svn commit: r40754 - head/en_US.ISO8859-1/books/faq
Eitan Adler
eadler at FreeBSD.org
Sat Jan 26 19:35:23 UTC 2013
Author: eadler
Date: Sat Jan 26 19:35:22 2013
New Revision: 40754
URL: http://svnweb.freebsd.org/changeset/doc/40754
Log:
nlist failed is not an FAQ these days.
Noted by: imp
Approved by: bcr (mentor, implicit)
Modified:
head/en_US.ISO8859-1/books/faq/book.xml
Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 18:58:03 2013 (r40753)
+++ head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 19:35:22 2013 (r40754)
@@ -2530,44 +2530,6 @@ bindkey ^[[3~ delete-char # for xterm</p
</qandaentry>
<qandaentry>
- <question id="nlist-failed">
- <para>Why do I get the error <errorname>nlist
- failed</errorname> 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
- <maketarget>installworld</maketarget>, 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
- <filename>boot2</filename> (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>
-
- <qandaentry>
<question id="connection-delay">
<para>Why does it take so long to connect to my computer via
<command>ssh</command> or <command>telnet</command>?</para>
More information about the svn-doc-head
mailing list