From: Arjan van de Ven <arjanv@redhat.com>
To: Nicklas Bondesson <nicke@nicke.nu>
Cc: "'Christophe Saout'" <christophe@saout.de>, linux-kernel@vger.kernel.org
Subject: Re: ataraid in 2.6.?
Date: Mon, 29 Dec 2003 18:30:12 +0100 [thread overview]
Message-ID: <20031229173012.GB21479@devserv.devel.redhat.com> (raw)
In-Reply-To: <200312291727.hBTHRDA13745@mx1.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On Mon, Dec 29, 2003 at 06:27:08PM +0100, Nicklas Bondesson wrote:
> How do you set this (device mapping) up using the 2.6 kernel. I like the
> ease of using ataraid in 2.4.x. Why not have both alternatives as options
> (both ataraid and devicemapper)?
because ataraid is nothing more than a devicemapper....
duplicating that is rather silly...
The outcome is to be a /sbin/ataraid binary or some such that will do all
the magic to detect the raid and tell the kernel device mapper to set it all
up.
> Also have anyone of you looked at the patch
> from Walt H that he sent in yesterday? I have to use this after replacing my
> old hard drives (Maxtor 30GB) with WDC 80GB. The patch is attached.
I sent it to Marcelo for applying last week, and he applied it today
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-29 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 0:09 ataraid in 2.6.? Nicklas Bondesson
2003-12-29 9:49 ` Arjan van de Ven
2003-12-29 12:59 ` Nicklas Bondesson
2003-12-29 17:08 ` Christophe Saout
2003-12-29 17:17 ` Arjan van de Ven
2003-12-29 17:27 ` Nicklas Bondesson
[not found] ` <200312291727.hBTHRDA13745@mx1.redhat.com>
2003-12-29 17:30 ` Arjan van de Ven [this message]
2003-12-29 21:43 ` Nicklas Bondesson
2003-12-29 22:18 ` Nicklas Bondesson
-- strict thread matches above, loose matches on Subject: below --
2003-12-29 17:35 Christophe Saout
2003-12-29 22:28 Christophe Saout
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=20031229173012.GB21479@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=christophe@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nicke@nicke.nu \
/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.