summaryrefslogtreecommitdiffstats
path: root/share/man/man9/cd.9
diff options
context:
space:
mode:
authorhmp <hmp@FreeBSD.org>2004-05-05 10:47:19 +0000
committerhmp <hmp@FreeBSD.org>2004-05-05 10:47:19 +0000
commitfb743e17de1f708a45750049683c795deb77c905 (patch)
treef127b925493a001faed19817795b49fd41c0accb /share/man/man9/cd.9
parentb13085958e9ed77ae81ed6a6c08e611d27a0a949 (diff)
downloadFreeBSD-src-fb743e17de1f708a45750049683c795deb77c905.zip
FreeBSD-src-fb743e17de1f708a45750049683c795deb77c905.tar.gz
mdoc(7) police:
* correctly place parenthisized sentences * remove hard sentence breaks * use .Vt instead of .Fn
Diffstat (limited to 'share/man/man9/cd.9')
-rw-r--r--share/man/man9/cd.98
1 files changed, 6 insertions, 2 deletions
diff --git a/share/man/man9/cd.9 b/share/man/man9/cd.9
index d52e47b..f86344b 100644
--- a/share/man/man9/cd.9
+++ b/share/man/man9/cd.9
@@ -90,9 +90,13 @@ The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands.
First, it
issues a CAM Path Inquiry command to determine whether the protocol that
-the drive speaks typically only allows 10 byte commands. (ATAPI and USB
+the drive speaks typically only allows 10 byte commands.
+.Po
+ATAPI and USB
are two prominent examples of protocols where you generally only want to
-send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
+send 10 byte commands.
+.Pc
+Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10
byte version of the command instead.
The only reason you would need a
OpenPOWER on IntegriCloud