All of lore.kernel.org
 help / color / mirror / Atom feed
* Deletion of 2.4 Linux sparse tree
@ 2005-10-05 12:53 Keir Fraser
  2005-10-06 19:36 ` Nivedita Singhvi
  0 siblings, 1 reply; 7+ messages in thread
From: Keir Fraser @ 2005-10-05 12:53 UTC (permalink / raw)
  To: xen-devel List

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: Deletion of 2.4 Linux sparse tree
@ 2005-10-05 23:56 James Harper
  2005-10-06  9:04 ` Keir Fraser
  2005-10-06 11:47 ` Mark Williamson
  0 siblings, 2 replies; 7+ messages in thread
From: James Harper @ 2005-10-05 23:56 UTC (permalink / raw)
  To: Keir Fraser, xen-devel List

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Deletion of 2.4 Linux sparse tree
  2005-10-05 23:56 James Harper
@ 2005-10-06  9:04 ` Keir Fraser
  2005-10-06 16:38   ` Andrei Petrov
  2005-10-06 11:47 ` Mark Williamson
  1 sibling, 1 reply; 7+ messages in thread
From: Keir Fraser @ 2005-10-06  9:04 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel List


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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Deletion of 2.4 Linux sparse tree
  2005-10-05 23:56 James Harper
  2005-10-06  9:04 ` Keir Fraser
@ 2005-10-06 11:47 ` Mark Williamson
  1 sibling, 0 replies; 7+ messages in thread
From: Mark Williamson @ 2005-10-06 11:47 UTC (permalink / raw)
  To: xen-devel; +Cc: James Harper

> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Deletion of 2.4 Linux sparse tree
  2005-10-06  9:04 ` Keir Fraser
@ 2005-10-06 16:38   ` Andrei Petrov
  0 siblings, 0 replies; 7+ messages in thread
From: Andrei Petrov @ 2005-10-06 16:38 UTC (permalink / raw)
  To: James Harper; +Cc: xen-devel List

> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Deletion of 2.4 Linux sparse tree
  2005-10-05 12:53 Deletion of 2.4 Linux sparse tree Keir Fraser
@ 2005-10-06 19:36 ` Nivedita Singhvi
  2005-10-08 10:53   ` Mark Williamson
  0 siblings, 1 reply; 7+ messages in thread
From: Nivedita Singhvi @ 2005-10-06 19:36 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel List

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Deletion of 2.4 Linux sparse tree
  2005-10-06 19:36 ` Nivedita Singhvi
@ 2005-10-08 10:53   ` Mark Williamson
  0 siblings, 0 replies; 7+ messages in thread
From: Mark Williamson @ 2005-10-08 10:53 UTC (permalink / raw)
  To: xen-devel

> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2005-10-08 10:53 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-05 12:53 Deletion of 2.4 Linux sparse tree Keir Fraser
2005-10-06 19:36 ` Nivedita Singhvi
2005-10-08 10:53   ` Mark Williamson
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05 23:56 James Harper
2005-10-06  9:04 ` Keir Fraser
2005-10-06 16:38   ` Andrei Petrov
2005-10-06 11:47 ` Mark Williamson

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.