[7986] in linux-scsi channel archive
Re: Devices not supporting read-6....
daemon@ATHENA.MIT.EDU (Drew Eckhardt)
Wed Feb 2 00:49:58 2000
Message-Id: <200002020540.WAA18341@chopper.poohsticks.org>
To: Jonas Nickel <jonas.nickel@tu-berlin.de>
Cc: R.E.Wolff@BitWizard.nl (Rogier Wolff),
linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu,
phoenix@thesindicate.com
In-reply-to: Your message of "Fri, 21 Jan 2000 10:33:36 +0100."
<3.0.6.32.20000121103336.00977100@sp.zrz.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18338.949470026.1@chopper.Poohsticks.ORG>
Date: Tue, 01 Feb 2000 22:40:26 -0700
From: Drew Eckhardt <drew@Poohsticks.Org>
In The Beginning (late 1991), Linux developers were chronically broke college
students running whatever obsolete hardware we managed to scrounge up.
In the SCSI-1 spec that some of this conformed to, Read-6 was required.
Read-10 was suggested as a good idea. Since some devices Wedged until
power cycled when fed a command they didn't support, I figured that
using Read-6 until we absolutely positively had to use Read-10 was a
fine idea.
In the 00's, it's probably a better idea to always use Read-10 unless
we're talking to a SCSI-1 device with READ CAPACITY returning a size
that can be accessed with Read-6 commands.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
