public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leonid Mamchenkov <f.l.linux-admin@news.francoudi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Updating the kernel of a RedHat 7.3
Date: Tue, 4 Mar 2003 17:27:32 +0000 (UTC)	[thread overview]
Message-ID: <20030304172732.GA20620@francoudi.com> (raw)
In-Reply-To: <3E64DC09.C15CC287@tid.es>

Dear Miguel Gonz?lez Casta?os,

Once you wrote about "Updating the kernel of a RedHat 7.3":
MGlCo>  I have followed the instructions of redhat of how to upgrade a kernel
MGlCo> downloading from the upgrades.redhat.com web page the corresponding
MGlCo> RPMs.

It looks like you haven't followed all instructions...

MGlCo>  I have downloaded the following RPMs for my fresh installation:
MGlCo>  kernel-2.4.18-24.7.x.i686.rpm
MGlCo>  kernel-source-2.4.18-24.7.x.i686.rpm
MGlCo>  kernel-smp-2.4.18-24.7.x.i686.rpm (since its a double proccesor box)

Sometimes you need a little more then that, like modutils, for example.

MGlCo>  I did the upgrade of the kernel-source RPM and had to use -ivh --nodeps
MGlCo> --force options to install the kernel and the kernel-smp RPMs.

Using either of --nodeps and --force is asking for troubles... not to
mention a combination of two.

MGlCo> 
MGlCo>  I noticed that the kernel progress bar only reached the 50%.

Bad sign.

MGlCo>  Everything seems to be fine, but what could be wrong or everything is
MGlCo> fine?

If you can run lilo without any complaints, I'd call it a pretty good
sign.  Otherwise, noone knows. :)

-- 
Best regards,
  Leonid Mamtchenkov, RHCE
  System Administrator
  Francoudi & Stephanou Ltd.


       reply	other threads:[~2003-03-04 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E64DC09.C15CC287@tid.es>
2003-03-04 17:27 ` Leonid Mamchenkov [this message]
2003-03-05  9:16   ` Updating the kernel of a RedHat 7.3 Leonid Mamchenkov

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=20030304172732.GA20620@francoudi.com \
    --to=f.l.linux-admin@news.francoudi.com \
    --cc=leonid@francoudi.com \
    --cc=linux-kernel@vger.kernel.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