From: Dave Jones <davej@suse.de>
To: Stuart MacDonald <stuartm@connecttech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] dd, floppy, 2.5.18
Date: Thu, 6 Jun 2002 20:53:52 +0200 [thread overview]
Message-ID: <20020606205352.C16262@suse.de> (raw)
In-Reply-To: <02aa01c20d86$ae9e8bc0$294b82ce@connecttech.com>
On Thu, Jun 06, 2002 at 02:19:22PM -0400, Stuart MacDonald wrote:
> I'm willing to help with some testing to figure out the problem; I use
> this dd method to make diskette images for customers all the time, and
> I will need it fixed for 2.6.x.
There's a patch included in 2.5.20-dj3 from Mikael Pettersson,
which should address the corruption on IO problem.
You can also fish out the individual patch at..
http://www.codemonkey.org.uk/patches/merged/2.5.20/dj3/
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-06-06 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 18:19 [BUG] dd, floppy, 2.5.18 Stuart MacDonald
2002-06-06 18:53 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 18:48 Mikael Pettersson
2002-06-07 19:02 ` Stuart MacDonald
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=20020606205352.C16262@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stuartm@connecttech.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