Re: Interesting plight
On Sat, Jan 13, 2001 at 10:52:28AM -0600, Erich Zigler wrote: > Could something not be getting updated? I'm very confused here and at a > complete loss. Okay, I found the problem. I seemed to have gotten a extra COPTFLAGS in the bottom of my make.conf with some weird opts. So the kernel was being compiled with different optimizations then the world. This was fun. Thank you all for your help. -- Erich Zigler Hah! If they were going to do that, they'd be just as likely to buy some extra rope to keep the pigs from getting out of their rooftop aviary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Interesting plight
On Fri, Jan 12, 2001 at 01:37:04PM -0600, Timothy Legant wrote: > If these steps (in this order!) are what you've already done, let us > know. Otherwise, do them exactly in this order and you will have the > same version kernel and userland. I would like to thank everyone for their help in this matter. I have followed your directions explicitly and still get the same errors with ps and top. Could it be possible my procfs is corrupted. This is a standard FreeBSD install Im not runing linux procfs and I do have procfs compiled into the kernel. Could something not be getting updated? I'm very confused here and at a complete loss. -- Erich Zigler Censorship sucks^H^H^H^H^H is for your own good. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Interesting plight
> > 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 [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Interesting plight
On 12-Jan-01 Erich Zigler wrote: > 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. > > What is wrong? There are several possiblities.. 1) You didn't cvsup everything (kernel and userland source) 2) You did cvsup everything OK but didn't build and/or install a new kernel AND userland (ie buildworld, buildkernel, installkernel, installworld) 3) Someone broke stable. I bet its 1 or 2 though :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Interesting plight
"Erich Zigler" <[EMAIL PROTECTED]>: > 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. > > What is wrong? > > Why will it work on 4.2-RELEASE but not 4.2-STABLE? It sure sounds like your userland and kernel are out of sync. Are you absolutely sure you're building and installing a new kernel, and that you've rebooted? What's the timestamp on /kernel? Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Interesting plight
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. What is wrong? Why will it work on 4.2-RELEASE but not 4.2-STABLE? -- Erich Zigler To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
