linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Martins Krikis <mkrikis@yahoo.com>,
	marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29
Date: Sun, 06 Feb 2005 09:38:54 -0500	[thread overview]
Message-ID: <42062BFE.7070907@pobox.com> (raw)
In-Reply-To: <58cb370e050206044513eb7f89@mail.gmail.com>

Bartlomiej Zolnierkiewicz wrote:
> On Sun, 06 Feb 2005 10:27:56 +0100, Arjan van de Ven
> <arjan@infradead.org> wrote:
> 
>>On Sat, 2005-02-05 at 21:36 -0500, Jeff Garzik wrote:
>>
>>>Martins Krikis wrote:
>>>
>>>>Version 0.1.5 of the Intel Sofware RAID driver (iswraid) is now
>>>>available for the 2.4 series kernels at
>>>>http://prdownloads.sourceforge.net/iswraid/2.4.29-iswraid.patch.gz?download
>>>
>>>ACK from me
>>
>> personally I consider it a new feature, and I don't consider new
>>features like this appropriate for a 2.4 deep maintenance stream.
> 
> 
> I have the same opinion


It sorts sucks for users with that hardware.  The typical complaint 
comes from trying to share data between Windows and Linux, where "just 
use md" isn't a solution.

Without device mapper (another new feature) to enable dmraid, these 
users are just sorta S.O.L.

I consider it not a new feature, but a missing feature, since otherwise 
user data cannot be accessed in the RAID setups.

	Jeff



  reply	other threads:[~2005-02-06 14:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29  1:15 [ANNOUNCE] "iswraid" (ICHxR ataraid sub-driver) for 2.4.29 Martins Krikis
2005-02-06  2:36 ` Jeff Garzik
2005-02-06  9:27   ` Arjan van de Ven
2005-02-06 12:45     ` Bartlomiej Zolnierkiewicz
2005-02-06 14:38       ` Jeff Garzik [this message]
2005-02-06 14:48         ` Christoph Hellwig
2005-02-06 14:49         ` Arjan van de Ven
2005-02-06 15:03           ` Jeff Garzik
2005-02-06 15:19             ` Bartlomiej Zolnierkiewicz
2005-02-10 19:35               ` Bill Davidsen
2005-02-10 20:05                 ` Bartlomiej Zolnierkiewicz
2005-02-10 22:04                   ` Bartlomiej Zolnierkiewicz
2005-02-10 18:39                     ` Marcelo Tosatti
2005-02-10 23:28                       ` Bartlomiej Zolnierkiewicz
2005-02-10 20:33                         ` Marcelo Tosatti
2005-02-11 10:46                       ` Arjan van de Ven
2005-02-06 15:28             ` Arjan van de Ven
2005-02-06 15:50             ` Christoph Hellwig
2005-02-06 16:09               ` Jeff Garzik
2005-02-06 16:27                 ` Christoph Hellwig
2005-02-07 16:45           ` Marcelo Tosatti
2005-02-07 18:29           ` Martins Krikis
     [not found]             ` <bc8bcc5105020711081f1de175@mail.gmail.com>
2005-02-07 19:30               ` Martins Krikis

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=42062BFE.7070907@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=mkrikis@yahoo.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;
as well as URLs for NNTP newsgroup(s).