Bug 24823

Comment 1 John Baldwin 2001-02-03 05:43:34 UTC

On 03-Feb-01 dima@unixfreak.org wrote:
> 
>>Number:         24823
>>Category:       docs
>>Synopsis:       [PATCH] New FAQ entry about top(1) not working (``nlist''
>>errors)
>>Confidential:   no
>>Severity:       non-critical
>>Priority:       low
>>Responsible:    freebsd-doc
>>State:          open
>>Quarter:        
>>Keywords:       
>>Date-Required:
>>Class:          change-request
>>Submitter-Id:   current-users
>>Arrival-Date:   Fri Feb 02 21:10:01 PST 2001
>>Closed-Date:
>>Last-Modified:
>>Originator:     Dima Dorfman
>>Release:        FreeBSD 4.2-20010102-STABLE i386
>>Organization:
> Private
>>Environment:
> 
> Not relevant.
> 
>>Description:
> 
> If one loads the kernel directly from boot0 (not using /boot/loader),
> or if one screws up an upgrade and the kernel is out of synch with the
> userland, one can get weird errors from top(1) and some other programs
> about certain kernel symbols not being found.  This seems to come up
> on -questions every few weeks; this FAQ entry should explain the cause
> and solution.

s/boot0/boot2/g please.  boot0 is what you hit Fx at to choose slices, boot1 is
a small assembly stub you never see anything from, and boot2 is what you can
interrupt to load a kernel w/o loading the loader.

-- 

John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

> On 03-Feb-01 dima@unixfreak.org wrote:
> > If one loads the kernel directly from boot0 (not using /boot/loader),
> > or if one screws up an upgrade and the kernel is out of synch with the
> > userland, one can get weird errors from top(1) and some other programs
> > about certain kernel symbols not being found.  This seems to come up
> > on -questions every few weeks; this FAQ entry should explain the cause
> > and solution.
> 
> s/boot0/boot2/g please.  boot0 is what you hit Fx at to choose
> slices, boot1 is a small assembly stub you never see anything from,
> and boot2 is what you can interrupt to load a kernel w/o loading the
> loader.

Thanks!  Good to see that someone more knowledgeable than me is
actually reading this stuff!  Here's a patch against the patch (how
convenient, eh?); or you can find the corrected version at:
http://www.unixfreak.org/~dima/home/nlist-faq2.diff

Thanks again!

					Dima Dorfman
					dima@unixfreak.org


--- nlist-faq.diff	Mon Jan 29 17:34:27 2001
+++ nlist-faq2.diff	Fri Feb  2 21:53:06 2001
@@ -35,7 +35,7 @@
 +
 +            <listitem>
 +              <para>You are not using <command>/boot/loader</command> to load
-+                your kernel, but doing it directly from boot0 (see
++                your kernel, but doing it directly from boot2 (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

Comment 3 nik 2001-02-06 00:28:48 UTC

State Changed
From-To: open->closed

Committed, with two changes: 

1.  Use <errorname> for the error message text. 

2.  Use <maketarget> for the 'installworld' text.