From: "Eric D. Mudama" <edmudama@bounceswoosh.org>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: "Eric D. Mudama" <edmudama@bounceswoosh.org>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: Silicon Image 3512 & seagate ST3120026AS in 2.4.27-rc2
Date: Wed, 30 Jun 2004 08:33:03 -0600 [thread overview]
Message-ID: <20040630143303.GA32765@bounceswoosh.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0406291354410.25702-100000@sweetums.bluetronic.net>
On Tue, Jun 29 at 13:59, Ricky Beam wrote:
>Maxtor has a perminant entry on my shitlist following their 60% failure
>rate with their SATA drives (in bulk.) And seeing how Dell no longer
>builds systems with Maxtor drives adds weight to my listing :-) (Unless
>they are getting a damn good OEM deal from WD, I don't think cost was why
>they switched. Even Tivo switched to WD after the Maxtor/Quantum merge.)
There's always a group of people who have shitlisted brand X due to
the way something failed, this is especially common in disk drives.
I'm sorry you had the problems, but they're not indicitive of Maxtor
as a whole, or we wouldn't be in business at all. I'm not sure how
our account with Tivo looks, but last I heard we were still the #1
supplier of drives into settop boxes.
I do think our new MaxLine III is a pretty hot drive, and it supports
NCQ, (with big performance gains in server-type applications) so as
soon as Jeff can get the ahci driver into the kernel...
--eric
PS: If you have issues in the future, feel free to contact me at
work... firstname_lastname@maxtor.com, and I'll do what I can to try
to help.
--
Eric D. Mudama
edmudama@mail.bounceswoosh.org
next prev parent reply other threads:[~2004-06-30 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 6:09 David Jez
2004-06-29 8:24 ` David Jez
2004-06-29 16:11 ` Eric D. Mudama
2004-06-29 17:59 ` Ricky Beam
2004-06-30 14:33 ` Eric D. Mudama [this message]
2004-07-01 10:13 ` David Jez
2004-06-29 16:58 ` Jeff Garzik
2004-07-01 10:30 ` David Jez
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=20040630143303.GA32765@bounceswoosh.org \
--to=edmudama@bounceswoosh.org \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®