All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: John Levon <levon@movementarian.org>
Cc: Pascal Bouchareine <pascal@gandi.net>,
	xen-devel@lists.xensource.com,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH] [Xend] Move some backend configuration
Date: Thu, 2 Oct 2008 15:16:42 +0100	[thread overview]
Message-ID: <18660.55242.139685.704930@mariner.uk.xensource.com> (raw)
In-Reply-To: <20081002134536.GA32071@totally.trollied.org.uk>

John Levon writes ("Re: [Xen-devel] [PATCH] [Xend] Move some backend configuration"):
> On Thu, Oct 02, 2008 at 10:49:34AM +0100, Keir Fraser wrote:
> > Of course the one downside is that this slightly changes the guest-visible
> > interface since it can't scribble at will in /l/d/<domid> any more. I hope
> > noone was relying on that! If we need to open up some more specific subdirs
> > for write access, I will consider that.
> 
> We're writing to the following paths that aren't standard:
> 
> device-misc/vif/default-link
> hvmpv/{xpv,xdf,xpvd,xnf}/version

What are these and how are they used ?

>  (we could even document this stuff by expanding xenstore.txt ?)

xenstore.txt currently has only the xenstored<->domains protocol, and
doesn't specify the structure or meaning of the xenstore tree.

interface.tex is supposed to do the latter but it's hopelessly out of
date and of course no-one really wants to edit TeX when they update
anything.

If some kind soul were to make a stab at extracting the relevant
(true!) parts of interface.tex into a new .txt file that would be very
nice :-).

Ian.

  parent reply	other threads:[~2008-10-02 14:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 14:24 [PATCH] [Xend] Move some backend configuration Pascal Bouchareine
2008-09-30 14:43 ` John Levon
2008-09-30 14:48   ` Keir Fraser
2008-09-30 14:58     ` John Levon
2008-09-30 15:09       ` Keir Fraser
2008-09-30 15:14         ` Ian Jackson
2008-09-30 15:30         ` Daniel P. Berrange
2008-09-30 16:09           ` Keir Fraser
2008-09-30 16:35             ` John Levon
2008-09-30 17:21               ` Pascal Bouchareine
2008-09-30 16:35             ` Daniel P. Berrange
2008-09-30 16:39               ` John Levon
2008-09-30 16:46               ` Keir Fraser
2008-09-30 17:08                 ` Daniel P. Berrange
2008-09-30 17:09               ` Pascal Bouchareine
2008-10-02  9:34             ` Ian Jackson
2008-10-02  9:49               ` Keir Fraser
2008-10-02 10:16                 ` Pascal Bouchareine
2008-10-02 10:20                   ` Keir Fraser
2008-10-02 10:21                   ` Ian Jackson
2008-10-02 10:28                     ` Keir Fraser
2008-10-02 10:31                       ` Ian Jackson
2008-10-02 13:45                 ` John Levon
2008-10-02 14:04                   ` Keir Fraser
2008-10-02 14:09                     ` Keir Fraser
2008-10-02 15:09                     ` John Levon
2008-10-02 15:25                       ` Keir Fraser
2008-10-02 17:21                         ` John Levon
2008-10-02 14:16                   ` Ian Jackson [this message]
2008-09-30 15:11       ` Pascal Bouchareine
2008-09-30 15:02     ` Keir Fraser
2008-09-30 15:06       ` John Levon

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=18660.55242.139685.704930@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=berrange@redhat.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=levon@movementarian.org \
    --cc=pascal@gandi.net \
    --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.