From: Tupshin Harper <tupshin@tupshin.com>
To: sm229534@albany.edu
Cc: xen-devel@lists.xensource.com
Subject: Re: Porting 2.6.2 linux kernel to XEN
Date: Mon, 11 Apr 2005 18:06:07 -0700 [thread overview]
Message-ID: <425B1EFF.30202@tupshin.com> (raw)
In-Reply-To: <63193.24.194.226.17.1113235097.squirrel@24.194.226.17>
sm229534@albany.edu wrote:
>Hello all,
>
>I need to port a 2.6.2 kernel to the Xen architecture, since there aren't
>any patches or sparse tree for kernels below 2.6.9 I'd like to know why ?
>And also wether that endeavor has been attempted before?
>
>In any case pointers, Help, Advice would be greatly useful. I would like
>to end up with something like linux-2.6.2-xen-sparse.
>
>Please Help
>
>
>Sam
>
It would very likely be easier to forward port, or otherwise fix
whatever issues are preventing you from running a recent kernel than it
would be to back port xen to something so old. Also, should you really
be comfortable running a kernel that has many known bugs and security
vulnerabilities that have been fixed in the last 14 months?
-Tupshin
next prev parent reply other threads:[~2005-04-12 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 15:58 Porting 2.6.2 linux kernel to XEN sm229534
2005-04-12 1:06 ` Tupshin Harper [this message]
2005-04-12 2:25 ` sm229534
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=425B1EFF.30202@tupshin.com \
--to=tupshin@tupshin.com \
--cc=sm229534@albany.edu \
--cc=xen-devel@lists.xensource.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 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.