From: David Lloyd <dmlloyd@flurg.com>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: RE: Upgrading kernel across multiple machines
Date: Thu, 10 Aug 2006 08:13:57 -0500 [thread overview]
Message-ID: <1155215638.24896.3.camel@ultros> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA001167638@chicken.machinevisionproducts.com>
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
next prev parent reply other threads:[~2006-08-10 13:13 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 [this message]
2006-08-10 14:36 ` Brian McGrew
-- 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=1155215638.24896.3.camel@ultros \
--to=dmlloyd@flurg.com \
--cc=brian@visionpro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox