From: Crayon Shin Chan <crayon.shin.chan.uk@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev and usb stick/hdd
Date: Tue, 24 Jul 2007 21:03:55 +0800 [thread overview]
Message-ID: <200707242103.56666.crayon.shin.chan.uk@gmail.com> (raw)
In-Reply-To: <20070723212134.04b37486@krikkit.digimed.co.uk>
On Tuesday 24 July 2007 04:21, Neil Bothwick wrote:
> I broke a GB stick in a couple of months by writing 700MB
> files to it.
For reference, when it broke, what happened? Does it die outright, or do
you get intermittent failures?
--
Crayon
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-07-24 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 13:19 [gentoo-user] udev and usb stick/hdd Aleksey V. Kunitskiy
2007-07-21 14:15 ` Dirk Heinrichs
2007-07-21 15:16 ` Aleksey V. Kunitskiy
2007-07-22 7:20 ` Dirk Heinrichs
2007-07-22 14:27 ` Crayon Shin Chan
2007-07-22 20:10 ` Neil Bothwick
2007-07-23 18:12 ` maxim wexler
2007-07-23 18:58 ` Alan McKinnon
2007-07-23 20:21 ` Neil Bothwick
2007-07-24 13:03 ` Crayon Shin Chan [this message]
2007-07-24 14:48 ` Neil Bothwick
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=200707242103.56666.crayon.shin.chan.uk@gmail.com \
--to=crayon.shin.chan.uk@gmail.com \
--cc=gentoo-user@lists.gentoo.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