From: Timothy Shimmin <tes@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Barry Naujok <bnaujok@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsqa: call _notrun in common.dump if dump utils not found
Date: Tue, 25 Mar 2008 15:58:30 +1100 [thread overview]
Message-ID: <47E88676.7080006@sgi.com> (raw)
In-Reply-To: <47E87D97.9050900@sandeen.net>
Eric Sandeen wrote:
> Barry Naujok wrote:
>> On Tue, 25 Mar 2008 14:23:40 +1100, Timothy Shimmin <tes@sgi.com> wrote:
>>
>>> Thanks, Eric.
>>>
>>> On IRIX:
>>> > where xfsdump xfsrestore xfsinvutil
>>> /sbin/xfsdump
>>> /usr/sbin/xfsdump
>>> /sbin/xfsrestore
>>> /usr/sbin/xfsinvutil
>>> > ls -l /sbin/xfsdump
>>> lrwxr-xr-x ... /sbin/xfsdump -> ../usr/sbin/xfsdump*
>>>
>>> I'll add the IRIX xfsrestore path and wait for Russell or
>>> whoever to complain about BSD :)
>> common.config sets up environment variables for the various
>> tools used and can handle these paths. It has them for the
>> xfsprogs tools (XFS_REPAIR_PROG, XFS_DB_PROG, etc) but
>> nothing for the xfsdump tools.
>
> yeah, that may be better...
>
Okay. Fair point.
I'll change common.dump to use the XFSDUMP_PROG etc....
and common.config to set the PROG vars.
--Tim
next prev parent reply other threads:[~2008-03-25 4:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-23 3:34 [PATCH] xfsqa: call _notrun in common.dump if dump utils not found Eric Sandeen
[not found] ` <20080323054136.GA7529@puku.stupidest.org>
2008-03-23 20:29 ` Eric Sandeen
2008-03-25 3:23 ` Timothy Shimmin
2008-03-25 3:35 ` Barry Naujok
2008-03-25 4:20 ` Eric Sandeen
2008-03-25 4:58 ` Timothy Shimmin [this message]
2008-03-25 6:05 ` Timothy Shimmin
2008-03-25 12:54 ` Eric Sandeen
2008-03-25 23:57 ` Timothy Shimmin
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=47E88676.7080006@sgi.com \
--to=tes@sgi.com \
--cc=bnaujok@sgi.com \
--cc=sandeen@sandeen.net \
--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