From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>, fstests@vger.kernel.org
Subject: [PATCH] xfs/279: use MKFS_XFS_PROG, not hardcoded path
Date: Fri, 13 Jun 2014 16:10:42 -0500 [thread overview]
Message-ID: <539B68D2.2000300@sandeen.net> (raw)
I'm really not sure why this wasn't this way from the start.
On some systems it's in /usr/sbin, and the test fails.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/tests/xfs/279 b/tests/xfs/279
index 872f8be..cde7d21 100755
--- a/tests/xfs/279
+++ b/tests/xfs/279
@@ -62,7 +62,7 @@ _check_mkfs()
{
echo "==================="
echo "mkfs with opts: $@" | sed -e "s,/dev/sd.,DEVICE,"
- /sbin/mkfs.xfs $@ 2>/dev/null > $tmp.mkfs.full
+ $MKFS_XFS_PROG $@ 2>/dev/null > $tmp.mkfs.full
if [ $? -ne 0 ]; then
echo "Failed."
return
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-06-13 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 21:10 Eric Sandeen [this message]
2014-06-16 9:34 ` [PATCH] xfs/279: use MKFS_XFS_PROG, not hardcoded path Christoph Hellwig
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=539B68D2.2000300@sandeen.net \
--to=sandeen@sandeen.net \
--cc=fstests@vger.kernel.org \
--cc=xfs@oss.sgi.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