Bug 21753

Comment 1 Will Andrews 2000-10-04 16:00:18 UTC

State Changed
From-To: open->closed

You have to install updated binaries along with a new 
kernel if you updated sources.  Hence, you can't normally 
install a kernel built from newer sources and use it with 
a world based on older sources.  To really solve your 
problem, try running `make world'.

On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
> >Synopsis:       Proc size mismatch
[snip]
> 
> >Description:
> 
> 	After install new kernel, which was CVSed recently, at 30 Sep 2000,
>         ps says "Proc size mismatch (32736 total, 1048 chunks)"
> 
> >How-To-Repeat:
> 
> 	CVS new kernel.
>         Install.
>         Reboot.
>         See this message...
> 
> >Fix:
> 
> 	Return to 4.1-RELEASE kernel code

Wrong.

Fix:
	Always read /usr/src/UPDATING when rebuilding a kernel.

<a quote from /usr/src/UPDATING>
COMMON ITEMS:

        To build a kernel
        -----------------
        cd /usr/src
        # If you have not already done so, please buildworld here
        # You will also need to update your config file to 4.x.
<end of quote>
	
	Always upgrade your whole system when upgrading your kernel -
	there are almost certain to be changes in the system programs
	as well, especially if some important kernel structures have
	changed.

G'luck,
Peter

-- 
Hey, out there - is it *you* reading me, or is it someone else?

Peter Pentchev wrote:
> 
> On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
> > >Synopsis:       Proc size mismatch
> [snip]
> >
> > >Description:
> >
> >       After install new kernel, which was CVSed recently, at 30 Sep 2000,
> >         ps says "Proc size mismatch (32736 total, 1048 chunks)"
> >
> > >Fix:
> >
> >       Return to 4.1-RELEASE kernel code
> 
> Wrong.

Right. At least for me :-) When I saw it, I got very surprised, and
reboot from 4.1-RELEASE kernel fix this problem...

> 
>         Always upgrade your whole system when upgrading your kernel -
>         there are almost certain to be changes in the system programs
>         as well, especially if some important kernel structures have
>         changed.
> 

I *REALLY* need rebuild hundred of there binaries, many of them didn't
change?
-- 
   With Best Regards.
   Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514
   Granch Ltd. lead engineer, e-mail: achilov@granch.ru
   tel/fax (383-2) 24-2363

On Thu, Oct 05, 2000 at 12:58:29PM +0700, Rashid N. Achilov wrote:
> Peter Pentchev wrote:
> > 
> > On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
> > > >Synopsis:       Proc size mismatch
> > [snip]
> > >
> > > >Description:
> > >
> > >       After install new kernel, which was CVSed recently, at 30 Sep 2000,
> > >         ps says "Proc size mismatch (32736 total, 1048 chunks)"
> > >
> > > >Fix:
> > >
> > >       Return to 4.1-RELEASE kernel code
> > 
> > Wrong.
> 
> Right. At least for me :-) When I saw it, I got very surprised, and
> reboot from 4.1-RELEASE kernel fix this problem...

This is a workaround, not a fix.  A workaround, as in it lets you
continue with your *old* binaries and your *old* kernel, which of course
are in sync.  It does not 'fix' the problem as in let you make use
of the new features introduced in FreeBSD with the changes.

> > 
> >         Always upgrade your whole system when upgrading your kernel -
> >         there are almost certain to be changes in the system programs
> >         as well, especially if some important kernel structures have
> >         changed.
> > 
> 
> I *REALLY* need rebuild hundred of there binaries, many of them didn't
> change?

Well, there is always make -DNOCLEAN buildworld, which leaves all of
the /usr/obj tree intact (well, most of it, anyway :), and recompiles
only the programs that have changed.  If this should fail, then you
must rebuild the whole thing - but this only happens very rarely, when
major changes have been introduced.

Ah, and yes, judging from personal experience, it's better to run
mergemaster *before* the world build, so it can update make.conf *and*
the mtree files - this takes care of the case when a new directory
has been introduced in the tree and the build falls over for lack of
dependencies :)

G'luck,
Peter

-- 
I am not the subject of this sentence.