From: hpa@zytor.com (H. Peter Anvin)
To: linux-raid@vger.kernel.org
Subject: Re: Raidtools-1.00.3
Date: Wed, 12 May 2004 22:39:52 +0000 (UTC) [thread overview]
Message-ID: <c7u93o$3ds$1@terminus.zytor.com> (raw)
In-Reply-To: 4098E2D8.7070007@wasp.net.au
Followup to: <4098E2D8.7070007@wasp.net.au>
By author: Brad Campbell <brad@wasp.net.au>
In newsgroup: linux.dev.raid
>
> I'm just wondering as raidreconf relies pretty heavily at the moment on some of the raidtools
> infrastructure and I'm wondering what to do long term.
> I have added raid-6 support to raidtools and updated it to work with kernel 2.6 and LBD, but if the
> long term plan is to let it bitrot then perhaps I'd be better looking at migrating raidreconf to
> some other framework and try to make it use mdadm for the low level stuff.
>
> Ideas or suggestions?
>
Getting raidreconf into mdadm would be a very good thing, I think.
-hpa
prev parent reply other threads:[~2004-05-12 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 12:49 Raidtools-1.00.3 Brad Campbell
2004-05-12 22:39 ` H. Peter Anvin [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='c7u93o$3ds$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-raid@vger.kernel.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).