From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: alal@google.com, xfs@oss.sgi.com
Subject: Re: [PATCH 1/1] Fix the ltp Makefile to allow for installation of all non-c (scripts) files
Date: Thu, 14 Jul 2011 12:04:45 -0500 [thread overview]
Message-ID: <1310663085.2067.18.camel@doink> (raw)
In-Reply-To: <20110714145809.GB23587@infradead.org>
On Thu, 2011-07-14 at 10:58 -0400, Christoph Hellwig wrote:
> On Thu, Jul 14, 2011 at 02:03:26PM +1000, Dave Chinner wrote:
> > On Wed, Jul 13, 2011 at 11:43:36PM -0400, Christoph Hellwig wrote:
> > > I'm fine with enabling 080 by default, it passes for me.
> >
> > It needs /bin/sh -> /bin/bash conversion first - the current version
> > fails miserably without that on all my test systems....
>
> Does the simple s/sh/bash/ fix it for you?
Dave, I figured out that you must have been talking about
ltp/rwtest.sh needing to be converted to bash.
I got rid of my /bin/sh and /usr/bin/sh symlinks and tried it
out. Turns out I can make some progress on it, but I now
find that /usr/sbin/xfs_check specifies /bin/sh as its interpreter.
I got around that by using "xfs_repair -n" for XFS_CHECK_PROG,
and outside of it producing different output the test seems
to work OK.
What else, specifically are you running into? And if you
have trouble with the /bin/sh in rwtest.sh, why are you not
running into similar trouble with xfs_check? I don't mind
doing the fix, but now I'm not sure what's required.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-14 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 20:52 [PATCH 1/1] Fix the ltp Makefile to allow for installation of all non-c (scripts) files Akshay Lal
2011-07-13 12:13 ` Christoph Hellwig
2011-07-13 18:26 ` Alex Elder
2011-07-14 3:43 ` Christoph Hellwig
2011-07-14 4:03 ` Dave Chinner
2011-07-14 14:58 ` Christoph Hellwig
2011-07-14 17:04 ` Alex Elder [this message]
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=1310663085.2067.18.camel@doink \
--to=aelder@sgi.com \
--cc=alal@google.com \
--cc=hch@infradead.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