From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@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: Fri, 17 Jun 2011 08:45:24 +0100 [thread overview]
Message-ID: <4DFB0614.8090708@eu.citrix.com> (raw)
In-Reply-To: <1308058567.17937.92.camel@zakaz.uk.xensource.com>
On 06/14/2011 02:36 PM, Ian Campbell wrote:
> On Mon, 2011-06-13 at 09:58 +0100, Vincent Hanquez wrote:
> Oh, right, that makes sense, more so than the cfg file based scheme I
> suggested (although eventually I expect that the will be needed too to
> express the admin's wishes, that's not relevant here). Thanks for
> explaining the actual usage.
Right, I guess i should have started with that. it would have same us both some
time.
> 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.
>
> 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).
Yes. I don't mind too much about the details, /run (with a fallback to /var/run
for old distrib) is probably better indeed.
I'm not sure about xl, i had the idea that you have to switch away from xend
when using xl by using an initscript. If that's not the case, then probably
something internal would work.
>> This feature has been discussed with toolstack people, patch has been
>> send to maintainers already and it's about to be committed in one case
>> (on two) provided it pass my tests i've left running over the weekend.
>
> Sounds interesting, do you have a link? I didn't see anything in the
> xen-api archives, but perhaps it was elsewhere? (or is this a reference
> some other toolstack?)
No, unfortunately there's no record of the discussion since we had it directly.
The udev module has been merged in the XCP tree [1]; The "only" thing left is
switching the hotplug module to be using this module. In XCI the full patch is
in (but I don't have any public link to it).
[1]
https://github.com/xen-org/xen-api-libs/commit/d6db355a4df93fafcf42cfb05df92dbae6a3b8f2
--
Vincent
next prev parent reply other threads:[~2011-06-17 7:45 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
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 [this message]
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=4DFB0614.8090708@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Campbell@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).