From: Ian Campbell <Ian.Campbell@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 18:42:25 +0100 [thread overview]
Message-ID: <1307554945.4176.47.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <4DEFA993.1020803@eu.citrix.com>
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?
>
> Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
>
> diff --git a/tools/hotplug/Linux/xen-hotplug-common.sh b/tools/hotplug/Linux/xen-hotplug-common.sh
> index 370f9ad..e248cae 100644
> --- a/tools/hotplug/Linux/xen-hotplug-common.sh
> +++ b/tools/hotplug/Linux/xen-hotplug-common.sh
> @@ -22,6 +22,8 @@ dir=$(dirname "$0")
> . "$dir/xen-script-common.sh"
> . "$dir/locking.sh"
>
> +[ -f "$dir/NOEXE" ] && exit 0
> +
> exec 2>>/var/log/xen/xen-hotplug.log
>
> export PATH="${BINDIR}:${SBINDIR}:${LIBEXEC}:${PRIVATE_BINDIR}:/sbin:/bin:/usr/bin:/usr/sbin:$PATH"
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-06-08 17:42 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 [this message]
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
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=1307554945.4176.47.camel@dagon.hellion.org.uk \
--to=ian.campbell@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).