Re: Upgrading kernel across multiple machines

[Brian McGrew <brian@visionpro.com>]

We got the system working, well, two of the three are working now.

Yesterday I tarred over /lib/modules/2.6.16.16 and /boot/*2.6.16.16*.  This
morning I did a sum on the *2.6.16.16* files in /boot and they did not match
the originals (!?! go figure !?!) so I copied them over so they match and
the machine came right up.

Now we'll see if I can duplicate this on machine #3.

THANKS FOR ALL THE HELP!

:b!


On 8/10/06 6:13 AM, "David Lloyd" <dmlloyd@flurg.com> wrote:

> On Wed, 2006-08-09 at 17:18 -0700, Brian D. McGrew wrote:
>> I tried copying over the initrd as well as making a new one!
> 
> Ok.  The only reason I mention it is that in many cases, necessary boot
> modules are stored in /lib on the initrd image.  Failure to load such a
> module would show up early in the boot sequence, before "real" init
> started up.
> 
> - DML
> 


:b!

-- 
Brian McGrew    { brian@visionpro.com || brian@doubledimenison.com }

> Is he allowed a plea of insanity for a parking ticket?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/