From: Michael Thonke <iogl64nx@gmail.com>
To: ress.weber@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to plan a kernel update ?
Date: Thu, 08 Sep 2005 19:35:19 +0200 [thread overview]
Message-ID: <43207657.9020907@gmail.com> (raw)
In-Reply-To: <9c23279705090810123132447d@mail.gmail.com>
Hello,
I won't be harsh but google is your best friend and first source for it.
please take a look at:
http://linuxdevices.com/articles/AT3855888078.html
They have a good guide and what should need attention in migrating to Kernel 2.6
They also have related articles for drivers in Kernel 2.6,NPTL and such.
Best regards
--
Michael Thonke
Weber Ress schrieb:
>Hi,
>
>I'm responsible to planning a kernel upgrade in many servers, from 2.4
>version to 2.6.13 (last stable version), using Debian 3.1r0a
>
>My team has good technical skills, but they need to be led. I would
>like know, what's the best pratices and recommendations that a project
>manager need think BEFORE an kernel upgrade.
>
>A technical guy have a particular vision about this upgrade, but I
>will be very been thankful if I receive from this community another
>vision.. a vision centered in the project process (planning,
>executing, controlling) to make this activity successfully.
>
>Thank's !
>
>Weber Ress
>-
>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/
>
>
>
next prev parent reply other threads:[~2005-09-08 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 17:12 How to plan a kernel update ? Weber Ress
2005-09-08 17:35 ` Michael Thonke [this message]
2005-09-08 17:49 ` linux-os (Dick Johnson)
2005-09-08 18:55 ` Jesper Juhl
2005-09-09 17:54 ` Weber Ress
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=43207657.9020907@gmail.com \
--to=iogl64nx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ress.weber@gmail.com \
/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