RE: [Xen-devel] Deletion of 2.4 Linux sparse tree

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

This is a vague wishlist item for me, but what would it take to backport
the xen patches to the linux kernel to 2.0 or 2.2?

I ask because I have a client with an ancient SCO application that has
some historic data in it and it might just work under linux with iBCS,
which has long since disappeared.

Failing that, how will a kernel in a VMX domain see hardware? Would the
kernel need specific device drivers?

Would a Linux dom0 and a SCO domU cause a matter-antimatter-like
explosion? :)

James

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
> Sent: Wednesday, 5 October 2005 22:54
> To: xen-devel List
> Subject: [Xen-devel] Deletion of 2.4 Linux sparse tree
> 
> The linux 2.4 sparse tree has been broken for a long time now, and it
> is unlikely ever to be fixed. Unless anyone wants to volunteer to
> maintain the tree, I plan to delete it from the repository in the next
> day or so.
> 
>   -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel