From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Hanquez Subject: Re: [PATCH] add a way to disable xen's udev script. Date: Wed, 8 Jun 2011 21:33:57 +0100 Message-ID: <4DEFDCB5.4020301@eu.citrix.com> References: <4DEFA993.1020803@eu.citrix.com> <1307554945.4176.47.camel@dagon.hellion.org.uk> <4DEFCC40.3000103@eu.citrix.com> <1307562567.4176.57.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1307562567.4176.57.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 06/08/2011 08:49 PM, Ian Campbell wrote: >> 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. Unfortunately that's not possible since all the libs that we need to depend on (libxenctrl, etc.) in xen-utils-4.1 depends on the package that install the udev rules (xen-utils-common). There's more than likely a perfect way to splice the packages to make it a package issue only, however I'm not terribly interested in putting more efforts than a *trivial* 1 line change. > 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. Or realize that those scripts are an abomination in the first place and get rid of them. -- Vincent