From: Bob Proulx <bob@proulx.com>
To: xen-devel@lists.xen.org
Cc: Bob Proulx <bob@proulx.com>
Subject: [PATCH] vif-bridge: fix cut behavior change
Date: Fri, 9 Aug 2013 01:18:19 -0600 [thread overview]
Message-ID: <1376032699-9869-1-git-send-email-bob@proulx.com> (raw)
A recent change in GNU cut disallows use of a newline as a field
delimiter. Avoid the problematic use of cut in vif-bridge.
Signed-off-by: Bob Proulx <bob@proulx.com>
---
tools/hotplug/Linux/vif-bridge | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/hotplug/Linux/vif-bridge b/tools/hotplug/Linux/vif-bridge
index f489519..9a6f82a 100644
--- a/tools/hotplug/Linux/vif-bridge
+++ b/tools/hotplug/Linux/vif-bridge
@@ -37,8 +37,7 @@ bridge=$(xenstore_read_default "$XENBUS_PATH/bridge" "$bridge")
if [ -z "$bridge" ]
then
- bridge=$(brctl show | cut -d "
-" -f 2 | cut -f 1)
+ bridge=$(brctl show | awk 'NR==2{print$1}')
if [ -z "$bridge" ]
then
--
1.8.4.rc1
next reply other threads:[~2013-08-09 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 7:18 Bob Proulx [this message]
2013-08-13 20:21 ` [PATCH] vif-bridge: fix cut behavior change Ian Campbell
2013-08-20 15:04 ` Ian Campbell
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=1376032699-9869-1-git-send-email-bob@proulx.com \
--to=bob@proulx.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 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).