On Tuesday 17 July 2007 14:30, Neil Bothwick wrote:
> On Tue, 17 Jul 2007 07:20:06 -0500, Billy McCann wrote:
> > Hi Mick.   From what I understand, using oldconfig for major version
> > changes (.20 -> .21) is a bad idea.  Here's what I did.  It may be slow
> > and stupid but it worked like a charm.
>
> 2.6.20 to 2.6.21 is not a major version change, it's a minor one, and a
> single step minor change at that. 2.4 to 2.6 is a major change when
> oldconfig should not be used, but I've been using it since 2.6.verylow
> and the only time it caused a problem was when the SATA config was moved
> (which oldconfig was never designed to handle).
>
> .20 to .21 (and then .22) had zero problems with oldconfig.

Thanks Neil, same here with regards to using oldconfig for some years now.  
I've only used 2.4 for a few months and then moved on to 2.6.  Since then 
I've had no problems (with different boxen) until this happened.

It's not as if it starts to load the kernel and then fails.  It just stops 
before then.  Shall I wait for a future version?  Am I the only one here with 
running a PIII that won't boot this kernel?
-- 
Regards,
Mick