xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Vincent Hanquez <Vincent.Hanquez@eu.citrix.com>
Subject: Re: [PATCH 2 of 2] xencommons: Wait for xenstored to start before setting dom0 name
Date: Tue, 29 Jun 2010 16:06:56 +0100	[thread overview]
Message-ID: <C84FCAA0.18FFC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1277823737.31214.556.camel@zakaz.uk.xensource.com>

On 29/06/2010 16:02, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:

> because it broke something. The thread at
> http://lists.xensource.com/archives/html/xen-devel/2008-03/msg00758.html
> has more details.
> 
> I'm not especially inclined to fix the C xenstored, lets hasten the
> switch to oxenstored instead.

I'd suggest disabling C xenstored build by default and install xenstored as
a symlink to oxenstored.

 -- Keir

      reply	other threads:[~2010-06-29 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 13:56 [PATCH 0 of 2] xencommons init script improvements George Dunlap
2010-06-29 13:56 ` [PATCH 1 of 2] xencommons: Make init script more verbose George Dunlap
2010-06-29 13:56 ` [PATCH 2 of 2] xencommons: Wait for xenstored to start before setting dom0 name George Dunlap
2010-06-29 14:10   ` Ian Campbell
2010-06-29 14:37   ` Jeremy Fitzhardinge
2010-06-29 15:02     ` Ian Campbell
2010-06-29 15:06       ` Keir Fraser [this message]

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=C84FCAA0.18FFC%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Vincent.Hanquez@eu.citrix.com \
    --cc=jeremy@goop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).