All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Ewan Mellor <ewan@xensource.com>, John Levon <levon@movementarian.org>
Subject: Re: Solaris dom0 (was "Makefile reworking")
Date: Mon, 7 Nov 2005 12:44:27 -0600	[thread overview]
Message-ID: <200511071244.27268.hollisb@us.ibm.com> (raw)
In-Reply-To: <20051107151816.GA15574@trollied.org>

On Monday 07 November 2005 09:18, John Levon wrote:
> This is initial work towards a Solaris Domain 0. For that we most
> definitely want the tools and Xen itself compiling (and eventually,
> working) on Solaris. We could maintain this as a permanent fork, but
> that has all the disadvantages a fork usually does.

In that case, the mingling of threads and signals in xenstored (see "Make 
xenstored reopen its trace file on SIGHUP") may not be a good idea. I think 
that behavior varies across operating systems...

-- 
Hollis Blanchard
IBM Linux Technology Center

      reply	other threads:[~2005-11-07 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 14:44 [PATCH] Makefile reworking John Levon
2005-11-07 15:16 ` Keir Fraser
2005-11-07 15:18   ` John Levon
2005-11-07 18:44     ` Hollis Blanchard [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=200511071244.27268.hollisb@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=ewan@xensource.com \
    --cc=levon@movementarian.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 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.