This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] add a way to disable xen's udev script.

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] add a way to disable xen's udev script.
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Fri, 17 Jun 2011 18:23:22 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Vincent Hanquez <Vincent.Hanquez@xxxxxxxxxxxxx>
Delivery-date: Fri, 17 Jun 2011 10:24:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1308058567.17937.92.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Newsgroups: chiark.mail.xen.devel
References: <4DEFA993.1020803@xxxxxxxxxxxxx> <1307554945.4176.47.camel@xxxxxxxxxxxxxxxxxxxx> <4DEFCC40.3000103@xxxxxxxxxxxxx> <1307562567.4176.57.camel@xxxxxxxxxxxxxxxxxxxx> <4DEFDCB5.4020301@xxxxxxxxxxxxx> <1307605345.775.758.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DF08BF4.3010904@xxxxxxxxxxxxx> <1307611406.775.781.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DF09B50.1020401@xxxxxxxxxxxxx> <1307689982.12738.34.camel@xxxxxxxxxxxxxxxxxxxx> <4DF5D128.4030208@xxxxxxxxxxxxx> <1308058567.17937.92.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Ian Campbell writes ("Re: [Xen-devel] [PATCH] add a way to disable xen's udev 
> I think we could make it opt-in for toolstacks which want it rather than
> opt-out for those that don't, since only xend and xl want them (I
> think???) that seems like a manageable change. The xencommons initscript
> might work for touching the file, but perhaps the xend initscript and
> something internal to libxl/xl (which doesn't have it's own initscript)
> would be better. Only question is who removes it in the xl case.

xencommons seems like the right place to me at least for the moment.

If we want xencommons to do something more sophisticated it already
reads /etc/default/xen so it could look there to see which toolstack
was in use and decide accordingly whether to enable the udev scripts.

> Since the file is automatically managed I don't think /etc is the right
> place -- probably somewhere like /var/run (which handily gets it cleaned
> up on reboot too).



Xen-devel mailing list