From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: tytso@mit.edu, Christoph Hellwig <hch@infradead.org>,
ext4 development <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>, Giel de Nijs <giel@vectorwise.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 14:11:13 -0500 [thread overview]
Message-ID: <20100130191113.GC10181@infradead.org> (raw)
In-Reply-To: <4B647AFE.5000507@sandeen.net>
On Sat, Jan 30, 2010 at 12:31:26PM -0600, Eric Sandeen wrote:
> These are the deps that I know xfstests has, to build and to run:
>
> BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
> BuildRequires: libacl-devel, libattr-devel, libaio-devel
>
> Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
> Requires: bc, indent, quota
>
> which isn't so bad...
Doesn't seem to bad. Indent is afaik only needed for the weird 122 test
which doesn't apply to non-xfs filesystems.
> I'm not sure an xfsprogs dependency is so onerous; plenty has depended
> on e2fsprogs through the years and we've lived with that ;) But
> the lag time for xfsprogs to use released xfs_io functionality is a
> bit of a bummer.
>
> But I guess I don't have a great answer for who else uses xfs_io:
I use xfs_io in lots various local scripts. It's a really handly
tool for exercising some of the more weird I/O related syscalls.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
ext4 development <linux-ext4@vger.kernel.org>,
tytso@mit.edu, Giel de Nijs <giel@vectorwise.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 14:11:13 -0500 [thread overview]
Message-ID: <20100130191113.GC10181@infradead.org> (raw)
In-Reply-To: <4B647AFE.5000507@sandeen.net>
On Sat, Jan 30, 2010 at 12:31:26PM -0600, Eric Sandeen wrote:
> These are the deps that I know xfstests has, to build and to run:
>
> BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
> BuildRequires: libacl-devel, libattr-devel, libaio-devel
>
> Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
> Requires: bc, indent, quota
>
> which isn't so bad...
Doesn't seem to bad. Indent is afaik only needed for the weird 122 test
which doesn't apply to non-xfs filesystems.
> I'm not sure an xfsprogs dependency is so onerous; plenty has depended
> on e2fsprogs through the years and we've lived with that ;) But
> the lag time for xfsprogs to use released xfs_io functionality is a
> bit of a bummer.
>
> But I guess I don't have a great answer for who else uses xfs_io:
I use xfs_io in lots various local scripts. It's a really handly
tool for exercising some of the more weird I/O related syscalls.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-30 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:05 [PATCH] xfstests 224: test aio hole-fill at 4g Eric Sandeen
2010-01-29 20:05 ` Eric Sandeen
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 17:25 ` tytso
2010-01-30 17:25 ` tytso
2010-01-30 18:31 ` Eric Sandeen
2010-01-30 18:31 ` Eric Sandeen
2010-01-30 19:11 ` Christoph Hellwig [this message]
2010-01-30 19:11 ` Christoph Hellwig
2010-01-30 19:46 ` Eric Sandeen
2010-01-30 19:46 ` Eric Sandeen
2012-10-26 17:18 ` Rich Johnston
2012-10-26 17:52 ` Eric Sandeen
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=20100130191113.GC10181@infradead.org \
--to=hch@infradead.org \
--cc=giel@vectorwise.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
--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 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.