From owner-freebsd-stable Sat Jan 13 3: 1: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b044.neo.rr.com [24.93.181.44]) by hub.freebsd.org (Postfix) with ESMTP id D31DF37B400 for ; Sat, 13 Jan 2001 03:00:50 -0800 (PST) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id f0DAqWx31723; Sat, 13 Jan 2001 05:52:33 -0500 Date: Sat, 13 Jan 2001 05:52:32 -0500 (EST) From: Mike Nowlin To: Kal Torak Cc: Erich Zigler , stable@FreeBSD.ORG Subject: Re: Interesting plight In-Reply-To: <3A5EB434.865FC56F@quake.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A couple days ago I was mentioning about my ps and top problems. Well at the > > advice of a FreeBSD user I went and installed the bin distribution for > > 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > > I could ps and top and kill I was one happy guy. > > > > Well I cvsup'ed my source tree, and went through the process as is outlined > > in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > > procedure, and ps and top fail to work. > > This just doesnt make ANY sense... > If you really did follow the instructions everything SHOULD work fine, > I have cvsup'd many times and so long as you do it by the UPDATING file > I have never had any problems (besides new/changed driver issues)... I have a system that went from 3.0, through a bunch of upgrades to 3.5, to 4.0, now up to 4.2. The 4.1.1 that was currently running seemed to work OK, but if I did a build/install world/kernel for 4.2, ps, top, and a few relatives died with some nlist error. I finally fixed it with "rm -fR /usr/src", re-CVSup, and rebuild... SOMETHING wasn't getting updated as it should... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message