Deletion of 2.4 Linux sparse tree

Deletion of 2.4 Linux sparse tree

[Keir Fraser]

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

Re: Deletion of 2.4 Linux sparse tree

[Nivedita Singhvi]

Keir Fraser wrote:
> 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

Keir,

Hadn't MarkW volunteered to take that on? If not, disregard this
mail..

thanks,
Nivedita

Re: Deletion of 2.4 Linux sparse tree

[Mark Williamson]

> Hadn't MarkW volunteered to take that on? If not, disregard this
> mail..

Yeah, I'd been meaning to jump in here ;-)

I think it's best off being deleted until someone has time to fix it properly.  
I did some fixing on it but found way too much stuff was still changing 
underneath me to make catching it up really viable.  Right now, I'm not sure 
I have the time - I'll bear it in mind for later.

Cheers,
Mark

RE: Deletion of 2.4 Linux sparse tree

[James Harper]

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@lists.xensource.com [mailto:xen-devel-
> bounces@lists.xensource.com] 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@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Deletion of 2.4 Linux sparse tree

[Keir Fraser]

On 6 Oct 2005, at 00:56, James Harper wrote:

> 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? :)

Backporting to 2.0/2.2 would not be a simple task. You'd have to run 
them unmodified in a vmx domain, once that code has stabilised some 
more.

  -- Keir

Re: Deletion of 2.4 Linux sparse tree

[Andrei Petrov]

> On 6 Oct 2005, at 00:56, James Harper wrote:
> 
> >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.
> >

Try NetBSD, it has ibcs.

-Andrei

Re: Deletion of 2.4 Linux sparse tree

[Mark Williamson]

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

It'd need the drivers for the emulated hardware...  It wouldn't *have to* have 
Xen-aware drivers.

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

You might need to use the "xm litigate" command

Cheers,
Mark

> James
>
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-
> > bounces@lists.xensource.com] 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@lists.xensource.com
> > http://lists.xensource.com/xen-devel
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel