From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v4 3/4] libxl: call hotplug scripts from libxl for vbd
Date: Mon, 14 May 2012 15:20:34 +0100 [thread overview]
Message-ID: <4FB114B2.7090404@citrix.com> (raw)
In-Reply-To: <20401.4940.65294.822388@mariner.uk.xensource.com>
Ian Jackson escribió:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH v4 3/4] libxl: call hotplug scripts from libxl for vbd"):
>> On Mon, 2012-05-14 at 13:38 +0100, Roger Pau Monne wrote:
>>> Are you sure about this? This command never returns anything, because it
>>> is redirected to /dev/null, so we only evaluate if it is able to read
>>> libxl/disable_udev. If libxl/disable_udev exists this test is passed.
>> You don't need the backticks for that though. With the backticks it will
>> execute whatever happens to be in the key -- I guess it's something
>> quite benign right now or you'd have seen errors.
>
> In fact Roger was right on the narrow point: because the>/dev/null is
> inside the backticks, the backticks never see any output and it's
> equivalent to `false` or `true`. I'm pleased that it's not just me
> that read it the way you did at first :-).
The fact that it works is just a question of "luck", but the
construction is definitely wrong. I always forget that you don't need to
use the ` when testing in the conditional for the execution of a
command. Sorry about that.
> But you are of course right in that it's a silly construction. If the
> output is not wanted, `` should not be used.
>
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-14 14:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 11:28 [PATCH v4 0/4] libxl: call hotplug scripts from libxl Roger Pau Monne
2012-05-10 11:28 ` [PATCH v4 1/4] libxl: pass env vars to libxl__exec Roger Pau Monne
2012-05-10 16:03 ` Ian Jackson
2012-05-10 11:28 ` [PATCH v4 2/4] libxl: add libxl__xs_path_cleanup Roger Pau Monne
2012-05-10 16:05 ` Ian Jackson
2012-05-10 11:28 ` [PATCH v4 3/4] libxl: call hotplug scripts from libxl for vbd Roger Pau Monne
2012-05-10 16:30 ` Ian Jackson
2012-05-14 12:38 ` Roger Pau Monne
2012-05-14 12:51 ` Ian Campbell
2012-05-14 13:30 ` Roger Pau Monne
2012-05-14 14:14 ` Ian Jackson
2012-05-14 14:20 ` Roger Pau Monne [this message]
2012-05-14 14:12 ` Ian Jackson
2012-05-10 11:28 ` [PATCH v4 4/4] libxl: call hotplug scripts from libxl for vif Roger Pau Monne
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=4FB114B2.7090404@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.