From: Brian McGrew <brian@visionpro.com>
To: David Lloyd <dmlloyd@flurg.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Upgrading kernel across multiple machines
Date: Thu, 10 Aug 2006 07:36:56 -0700 [thread overview]
Message-ID: <C1009298.8D00%brian@visionpro.com> (raw)
In-Reply-To: <1155215638.24896.3.camel@ultros>
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?
next prev parent reply other threads:[~2006-08-10 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 0:18 Upgrading kernel across multiple machines Brian D. McGrew
2006-08-10 13:13 ` David Lloyd
2006-08-10 14:36 ` Brian McGrew [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 21:52 Brian McGrew
2006-08-09 22:03 ` Sam Ravnborg
2006-08-09 22:08 ` Brian McGrew
2006-08-09 22:18 ` David Lloyd
2006-08-09 22:07 ` Randy.Dunlap
2006-08-09 22:10 ` Brian McGrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1009298.8D00%brian@visionpro.com \
--to=brian@visionpro.com \
--cc=dmlloyd@flurg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.