From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mhw@wittsend.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Sync option destroys flash!
Date: Fri, 13 May 2005 23:00:34 +0100 [thread overview]
Message-ID: <1116021632.20550.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1116011430.5239.108.camel@localhost.localdomain>
On Gwe, 2005-05-13 at 20:10, Michael H. Warfield wrote:
> > It sounds like your need to find a vendor who makes decent keys. For
> > that matter several vendors now offer life time guarantees with their
> > USB flash media.
>
> Now THAT I gotta check into. I never noticed anything on the packaging
> about a guarantee, but I will now.
Most of them have guarantees of some form (this URL might be useful
since it lists the guarantee times for a lot of the media - EU
guarantees anyway, US often seem to be a lot different)
http://www.valuemedia.co.uk/compact_flash.htm
As you'll see Lexar for example offer lifetime guarantees on their
units. I believe Kingston also do.
> But how do you determine which are
> "decent" keys? They don't put stickers on them saying "this one is
> decent" and "this one is junk" and I'm an old cynic who has learned that
> price is not always a good indicator either. Maybe the guarantee will
> be a clue. I've just got to shop for it more.
Or it may even be cheaper to "burn" a few - buy one of each type from
various shops, do 2 million writes to the same sector and take them back
the next day if they died [And publish the review data 8))]
Alan
next prev parent reply other threads:[~2005-05-13 22:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 16:20 Sync option destroys flash! Michael H. Warfield
2005-05-13 17:17 ` Lennart Sorensen
2005-05-13 17:53 ` Michael H. Warfield
2005-05-13 18:09 ` Lennart Sorensen
2005-05-13 18:21 ` Michael H. Warfield
2005-05-13 18:26 ` Lennart Sorensen
2005-05-13 18:52 ` Flash device types Mark Rustad
2005-05-13 18:53 ` Sync option destroys flash! Michael H. Warfield
2005-05-13 17:58 ` Zan Lynx
2005-05-13 18:13 ` Lennart Sorensen
2005-05-13 18:40 ` Alan Cox
2005-05-13 19:10 ` Michael H. Warfield
2005-05-13 22:00 ` Alan Cox [this message]
2005-05-13 22:22 ` Måns Rullgård
2005-05-13 23:24 ` Jon Masters
2005-05-13 23:01 ` Jeffrey Hundstad
2005-05-13 23:27 ` Jon Masters
2005-05-14 10:17 ` Jörn Engel
2005-05-14 1:05 ` Michael H. Warfield
2005-05-17 13:30 ` Lennart Sorensen
2005-05-13 21:25 ` Lee Revell
2005-05-13 22:43 ` Alan Cox
2005-05-15 19:00 ` Denis Vlasenko
2005-05-16 0:23 ` Mark Lord
2005-05-16 9:29 ` David Woodhouse
2005-05-16 16:42 ` Pavel Machek
2005-05-16 13:01 ` Richard B. Johnson
2005-05-16 23:18 ` Helge Hafting
2005-05-18 7:03 ` Denis Vlasenko
2005-05-17 7:59 ` Colin Leroy
[not found] <43Ldl-NM-25@gated-at.bofh.it>
[not found] ` <43M9s-1B8-39@gated-at.bofh.it>
[not found] ` <43MCx-1UF-27@gated-at.bofh.it>
[not found] ` <43MVz-2hL-1@gated-at.bofh.it>
2005-05-13 23:59 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2005-05-14 2:43 linux
2005-05-17 13:36 ` Lennart Sorensen
2005-05-17 20:31 ` linux
2005-05-17 20:43 ` Richard B. Johnson
2005-05-18 13:37 ` Lennart Sorensen
[not found] <43UT5-jT-3@gated-at.bofh.it>
2005-05-14 4:34 ` Robert Hancock
2005-05-18 11:13 linux
2005-05-18 12:01 ` Richard B. Johnson
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=1116021632.20550.11.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mhw@wittsend.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