From: Mark <mark@harddata.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Upgrade from 2.4.25 to 2.6.4 kernel
Date: Thu, 1 Apr 2004 15:24:12 -0700 [thread overview]
Message-ID: <200404011524.12034.mark@harddata.com> (raw)
In-Reply-To: <20040401205344.546715FB7B@mail.metropipe.net>
On April 1, 2004 03:49 pm, "Job 317" <job317@mailvault.com> wrote:
> Hello list.
>
> Can someone please point me to a HOWTO on installing a 2.6.x kernel on a
> system that heretofore runs a 2.4.x kernel?
http://kerneltrap.org/node/view/799
BTW Google is your friend here. Do a search for 2.6 HOWTO and that link is the
first one on the list.
>
> NOT a howto on building the kernel. I'm o.k. there. But I understand
> that it is not the same upgrading to a 2.6.x kernel as it is just
> upgrading to the next 2.4.x kernel. Is this correct?
No, a 2.6 kernel will run without changes to RedHat 9 but some changes should
be made.
> Aren't there
> startup scripts and things that rely on the 2.4.x structure that change
> slightly for a 2.6.x kernel?
>
Yes, check out the link above. There are also some links to RedHat 9 specific
instructions.
> !!!!Also... is it possible to still to boot back to a 2.4.x kernel in
> this case?
Yep you can still run a 2.4.x kernel.
> Lets say I keep my 2.4.25 kernel that I built on my RedHat 9
> box. Can I also boot to and from my 2.6.x kernel?
Yes
--
Mark Lane, CET mailto:mark@harddata.com
Hard Data Ltd. http://www.harddata.com
T: 01-780-456-9771 F: 01-780-456-9772
11060 - 166 Avenue Edmonton, AB, Canada, T5X 1Y3
--> Ask me about our Excellent 1U Systems! <--
next prev parent reply other threads:[~2004-04-01 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 20:49 Upgrade from 2.4.25 to 2.6.4 kernel Job 317
2004-04-01 22:24 ` Mark [this message]
2004-04-01 22:31 ` Darren Williams
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 1:48 Job 317
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=200404011524.12034.mark@harddata.com \
--to=mark@harddata.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 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.