ps: proc size mismatch
I last did a buildworld, buildkernel, installkernel, installworld in December (from current STABLE sources via cvsup). I tried again a few weeks ago and today, and after booting to single-user get errors from ps about /proc (ps: proc size mismatch). uname from my working kernel world is: FreeBSD www.reppep.com 4.7-STABLE FreeBSD 4.7-STABLE #0: Tue Dec 3 14:05:51 EST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REPPEP i386 Commands I ran to update (in December successfully, and twice unsuccessfully this month): # more Makefile UPDATING # mergemaster -p ; make buildworld ~/buildworld-20030221.log ; make buildkernel ~/buildkernel-20030221.log # mergemaster found no changes # mergemaster -p # no changes found # make installkernel Searching the web, I see many people saying if ps complains about a mismatch, your world is out of sync with the kernel http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-trouble.html#KERNELCONFIG-NOBOOT. I know that, because I haven't done make installworld yet, but I'm trying to validate the new kernel first. Unfortunately, there isn't much info on how to validate the kernel (if it boots to the shell, is it fine??). Is there anything else I should test before make installworld? Thank you, Chris Pepper PS-Please cc me directly. -- Chris Pepper: http://www.reppep.com/~pepper/ Rockefeller University: http://www.rockefeller.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ps: proc size mismatch
On 2003-02-22 21:24, Chris Pepper [EMAIL PROTECTED] wrote: Commands I ran to update (in December successfully, and twice unsuccessfully this month): # more Makefile UPDATING # mergemaster -p ; make buildworld ~/buildworld-20030221.log ; make buildkernel ~/buildkernel-20030221.log # mergemaster found no changes # mergemaster -p # no changes found # make installkernel The proc size mismatch you're seeing is because your kernel and userland is not in sync. Reboot. Enter single user mode. Run 'installworld'. If you suspect 'installworld' can fail in the middle of it all, and leave you with a useless installation, half-updated and half-not, then make sure you have about 300 MB of free space in /somewhere and run: # cd /usr/src # make DESTDIR=/somewhere installworld if this works fine, then youcan safely delete everything in /somewhere and run the real 'installworld' without DESTDIR. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ps: proc size mismatch
In [EMAIL PROTECTED], Chris Pepper [EMAIL PROTECTED] typed: I know that, because I haven't done make installworld yet, but I'm trying to validate the new kernel first. Unfortunately, there isn't much info on how to validate the kernel (if it boots to the shell, is it fine??). It's a pretty good indication, but not definite. I once tripped over a bug in a SCSI driver that caused failures under load, so I could do an installworld but not a buildworld. If you've got the time, you can always try running a buildworld on the new kernel. That's a thorough stress test. Is there anything else I should test before make installworld? Any hardware not touched in getting to the shell prompt that *has* to be working on your system. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: ps: proc size mismatch
At 5:09 AM +0200 2003/02/23, Giorgos Keramidas wrote: On 2003-02-22 21:24, Chris Pepper [EMAIL PROTECTED] wrote: Commands I ran to update (in December successfully, and twice unsuccessfully this month): # more Makefile UPDATING # mergemaster -p ; make buildworld ~/buildworld-20030221.log ; make buildkernel ~/buildkernel-20030221.log # mergemaster found no changes # mergemaster -p # no changes found # make installkernel The proc size mismatch you're seeing is because your kernel and userland is not in sync. Reboot. Enter single user mode. Run 'installworld'. If you suspect 'installworld' can fail in the middle of it all, and leave you with a useless installation, half-updated and half-not, then make sure you have about 300 MB of free space in /somewhere and run: # cd /usr/src # make DESTDIR=/somewhere installworld if this works fine, then youcan safely delete everything in /somewhere and run the real 'installworld' without DESTDIR. So (aside from verifying sufficient free space), the only test to do after installkernel and before installworld is to make sure that the system can boot single-user? Thanks, Chris -- Chris Pepper: http://www.reppep.com/~pepper/ Rockefeller University: http://www.rockefeller.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
