All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Olaf Hering <olaf@aepfle.de>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	xen-devel@lists.xensource.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] disable kernel build in Xen build system / Xen dom0 kernel versions
Date: Fri, 10 Sep 2010 15:06:57 +0300	[thread overview]
Message-ID: <20100910120657.GV2804@reaktio.net> (raw)
In-Reply-To: <20100910115741.GA26743@aepfle.de>

On Fri, Sep 10, 2010 at 01:57:41PM +0200, Olaf Hering wrote:
> On Fri, Sep 10, George Dunlap wrote:
> 
> > I think it's a good idea for the Xen build system not to include a
> > dom0 kernel.  However, it's not very clear to a newcomer how to
> > actually get a kernel.  The xen.org download page has no links at all
> > to anything kernel-related.  There is a page on the wiki:
> > 
> >  http://wiki.xensource.com/xenwiki/XenDom0Kernels
> > 
> > However, the list is gigantic -- extremely intimidating.  And there's
> > no generic version of the "classic" kernel; they're all branded XCP,
> > XCI, Novell, &c.
> > 
> > I think the Right Thing to do (given an ideal world), until pvops dom0
> > gets sufficiently upstreamed, is for xen.org to maintain two stable
> > releases: a reasonably stable pvops branch for the more adventurous,
> > and a classic xen port for the more conservative.
> 
> George,
> 
> I second that. The first time I looked at this page all it caused was
> confusion. It gives the impression of "there is no upstream". If we
> could get some sort of reference where all the fixes go, that would help
> alot.
> I would help out with maintaining such a tree.
> 

Yeah, the XenDom0Kernels wiki page has gotten pretty unclear.

I guess for users, at the moment, the two 'main' kernels that
are maintained and bugfixed by xen.org are:

- pvops xen/stable-2.6.32.x
- xenlinux xcp/xenserver 2.6.32.x 

I can try to clear up the wiki page if we can agree on what to write there :)

-- Pasi

  reply	other threads:[~2010-09-10 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 10:09 [PATCH] disable kernel build in Xen build system Ian Campbell
2010-09-10 11:04 ` George Dunlap
2010-09-10 11:57   ` Olaf Hering
2010-09-10 12:06     ` Pasi Kärkkäinen [this message]
2010-09-10 12:35       ` [PATCH] disable kernel build in Xen build system / Xen dom0 kernel versions Ian Campbell
2010-09-21 16:30       ` Stefano Stabellini
2010-09-21 16:36         ` Pasi Kärkkäinen
2010-09-10 12:31   ` [PATCH] disable kernel build in Xen build system Ian Campbell
2010-09-10 17:52 ` Ian Jackson

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=20100910120657.GV2804@reaktio.net \
    --to=pasik@iki.fi \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=olaf@aepfle.de \
    --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.