xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Vincent Hanquez <Vincent.Hanquez@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] add a way to disable xen's udev script.
Date: Wed, 8 Jun 2011 20:49:27 +0100	[thread overview]
Message-ID: <1307562567.4176.57.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <4DEFCC40.3000103@eu.citrix.com>

On Wed, 2011-06-08 at 20:23 +0100, Vincent Hanquez wrote:
> On 06/08/2011 06:42 PM, Ian Campbell wrote:
> > On Wed, 2011-06-08 at 17:55 +0100, Vincent Hanquez wrote:
> >> Add a way to disable xen's udev scripts by using a dummy file.
> >
> > Why?
> >
> > Does one of "chmod -x" or "rm" not suffice?
> 
> Because it provides the ability to install side-by-side multiple 
> toolstacks, including one that doesn't use the xen's xend udev scripts.

> chmod -x and rm would do the same things (provided udev isn't unhappy), 
> but modifying files of package A from another package B is highly 
> frowned upon.

Dropping down a file which unilaterally disables critical behaviour in
another package requires isn't really much better, you might as well
just add a Conflicts: and be done with it.

In
http://lists.alioth.debian.org/pipermail/pkg-xen-devel/2011-April/003362.html the Debian package maintainer proposed a scheme by which xm and xl could coexist. Adding "xapi" (or whichever other toolstack you are considering) as an option to that scheme and having all the sets of hotplug scripts check that their scheme is active seems like a reasonable solution to me.

Of course in the longer term we should attempt to converge the hotplug
scripts of the different toolstacks into a single set of (e.g. libxl
based) scripts.

Ian.

  reply	other threads:[~2011-06-08 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 16:55 [PATCH] add a way to disable xen's udev script Vincent Hanquez
2011-06-08 17:42 ` Ian Campbell
2011-06-08 19:23   ` Vincent Hanquez
2011-06-08 19:49     ` Ian Campbell [this message]
2011-06-08 20:33       ` Vincent Hanquez
2011-06-09  7:42         ` Ian Campbell
2011-06-09  9:01           ` Vincent Hanquez
2011-06-09  9:23             ` Ian Campbell
2011-06-09 10:07               ` Vincent Hanquez
2011-06-10  7:13                 ` Ian Campbell
2011-06-13  8:58                   ` Vincent Hanquez
2011-06-14 13:36                     ` Ian Campbell
2011-06-17  7:45                       ` Vincent Hanquez
2011-06-17 17:23                       ` 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=1307562567.4176.57.camel@dagon.hellion.org.uk \
    --to=ian.campbell@eu.citrix.com \
    --cc=Vincent.Hanquez@eu.citrix.com \
    --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).