From owner-freebsd-doc Fri Feb 2 22: 0:20 2001 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1B85237B401 for ; Fri, 2 Feb 2001 22:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f13603R91508; Fri, 2 Feb 2001 22:00:03 -0800 (PST) (envelope-from gnats) Date: Fri, 2 Feb 2001 22:00:03 -0800 (PST) Message-Id: <200102030600.f13603R91508@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Dima Dorfman Subject: Re: docs/24823: [PATCH] New FAQ entry about top(1) not working ( Reply-To: Dima Dorfman Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR docs/24823; it has been noted by GNATS. From: Dima Dorfman To: John Baldwin Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: docs/24823: [PATCH] New FAQ entry about top(1) not working ( Date: Fri, 02 Feb 2001 21:59:41 -0800 > 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 @@ + + + You are not using /boot/loader 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 + /boot/loader, it generally does a better + job of making the kernel symbols available to user To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message