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: Thu, 9 Jun 2011 10:01:40 +0100 [thread overview]
Message-ID: <4DF08BF4.3010904@eu.citrix.com> (raw)
In-Reply-To: <1307605345.775.758.camel@zakaz.uk.xensource.com>
On 06/09/2011 08:42 AM, Ian Campbell wrote:
> and of course working with the maintainer of the package you wish to
> integrate with is clearly out of the question?
This is an upstream issue in the first place. The assumption that
everyone is supposed to use those *globally* installed udev scripts that
are targeted to xend and to some extent xl, is simply false.
While i used the debian package as an example, the same is true for
every other xen packages that i looked at.
And adding a Conflicts entry is just not a solution either, since you
need install/removes packages (and restarting udev) to switch toolstacks
whereas my solution involves no such thing.
In any case, installing multiple toolstacks in parallel would *have* to
have a *dynamic* way to execute different udev scripts, which I might
argue that's exactly what i provide in a very simple way with a dummy
file mechanism (not ideal mechanism, but just does the job trivially).
>> 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.
>
> Sorry, but I don't think you motivation or lack thereof justifies adding
> this sort of hack to the upstream Xen code base.
Please. joking so early !
Those scripts are hacks in the first place, and are taking advantages of
udev flexibility to do horrid stuff.
--
Vincent
next prev parent reply other threads:[~2011-06-09 9:01 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 [this message]
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=4DF08BF4.3010904@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).