8212 manpages contain obsolete references

6019 sleep can't be infinite
Reviewed by: Toomas Soome <tsoome@me.com>
Reviewed by: Yuri Pankov <yuripv@gmx.com>
Reviewed by: Alexander Pyhalov <alp@rsu.ru>
Approved by: Robert Mustacchi <rm@joyent.com>

1 files changed, 10 insertions, 39 deletions

diff --git a/usr/src/man/man7d/scsa2usb.7d b/usr/src/man/man7d/scsa2usb.7d
index 94903e0cbe..7a14176b7b 100644
--- a/usr/src/man/man7d/scsa2usb.7d
+++ b/usr/src/man/man7d/scsa2usb.7d
@@ -3,7 +3,7 @@
 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
-.TH SCSA2USB 7D "Jul 28, 2008"
+.TH SCSA2USB 7D "May 13, 2017"
 .SH NAME
 scsa2usb \- SCSI to USB bridge driver
 .SH SYNOPSIS
@@ -13,7 +13,6 @@ scsa2usb \- SCSI to USB bridge driver
 .fi
 
 .SH DESCRIPTION
-.sp
 .LP
 The \fBscsa2usb\fR driver is a \fBUSBA\fR (Solaris USB architecture) compliant
 nexus driver that supports the \fIUSB Mass Storage Bulk Only Transport
@@ -27,7 +26,7 @@ supports storage devices that utilize the above two transports.
 .sp
 .LP
 The \fBscsa2usb\fR driver also supports a \fBugen\fR(7D) interface allowing raw
-access to the device, for example by \fBlibusb\fR(3LIB) applications, bypassing
+access to the device, for example by libusb applications, bypassing
 the child \fBsd\fR(7D) or \fBst\fR(7D) driver. Because a libusb application
 might change the state of the device, you should not access the disk or tape
 concurrently.
@@ -55,8 +54,8 @@ In the current release, however, only disk storage devices with a removable bit
 INQUIRY data.) See SCSI specifications T10/995D Revision 11a, T10/1236-D
 Revision 20 or T10/1416-D Revision 23 for more information. However, for
 backward compatibility, all USB disk storage devices can still be managed by
-\fBrmformat\fR(1). With or without a volume  manager,  you can  mount, eject,
-hot remove and hot insert a  1394 mass storage device as the following sections
+\fBrmformat\fR(1). With or without a volume manager, you can mount, eject,
+hot remove and hot insert a 1394 mass storage device as the following sections
 explain.
 .sp
 .LP
@@ -72,8 +71,8 @@ enable support of particular devices.
 .sp
 .LP
 Follow the information given in the \fBscsa2usb.conf\fR file to see if a
-particular device can be supported using the override information. Also see
-http:/\fI/www.sun.com/io\fR. For example, by adding the following to the
+particular device can be supported using the override information.
+For example, by adding the following to the
 \fBscsa2usb.conf\fR file, many USB memory sticks and card readers might operate
 more reliably:
 .sp
@@ -104,7 +103,6 @@ exclude: scsa2usb
 Alternatively, you can disable automatic handling of a device as described in
 the following subsection.
 .SS "Using Volume Management"
-.sp
 .LP
 Disk storage devices are managed by Volume Manager. Software that manages
 removable media creates a device nickname that can be listed with
@@ -131,12 +129,7 @@ it.
 You can disable the automatic mounting and unmounting of removable devices by
 inserting a entry for a removable device in \fB/etc/vfstab\fR. In this entry,
 you must set the \fBmount at boot\fR field to \fBno\fR. See \fBvfstab\fR(4).
-See the \fISystem Administration Guide, Volume I\fR and \fISolaris Common
-Desktop Environment: User's Guide\fR for details on how to manage a removable
-device with CDE and Removable Media Manager. See \fBdtfile.1X\fR under CDE for
-information on how to use Removable Media Manager.
 .SS "Using \fBmount\fR and \fBumount\fR"
-.sp
 .LP
 Use \fBmount\fR(1M) to explicitly mount the device and \fBumount\fR(1M) to
 unmount the device. Use \fBeject\fR(1) to eject the media. After you have
@@ -148,12 +141,7 @@ Removing the disk device while it is being accessed or mounted fails with a
 console warning. To hot remove the disk device from the system, unmount the
 file system, then kill all applications accessing the device. Next, hot remove
 the device. A storage device can be hot inserted at any time.
-.sp
-.LP
-For a comprehensive listing of (non-bootable) USB mass-storage devices that are
-compatible with this driver, see \fBwww.sun.com/io\fR.
 .SH DEVICE SPECIAL FILES
-.sp
 .LP
 Disk block special file names are located in \fB/dev/dsk\fR, while raw file
 names are located in \fB/dev/rdsk\fR. Tape raw file names are located in
@@ -161,15 +149,12 @@ names are located in \fB/dev/rdsk\fR. Tape raw file names are located in
 restrictions as those for SCSI disks or tapes. Refer to \fBsd\fR(7D) or
 \fBst\fR(7D).
 .SH IOCTLS
-.sp
 .LP
 Refer to \fBdkio\fR(7I) and \fBcdio\fR(7I).
 .SH ERRORS
-.sp
 .LP
 Refer to \fBsd\fR(7D) for disks or \fBst\fR(7D) for tapes.
 .SH FILES
-.sp
 .LP
 The device special files for the USB mass storage device are created like those
 for a \fBSCSI\fR disk or SCSI tape. Refer to \fBsd\fR(7D) or \fBst\fR(7D).
@@ -285,7 +270,6 @@ Can be used to override specific characteristics.
 .RE
 
 .SH ATTRIBUTES
-.sp
 .LP
 See \fBattributes\fR(5) for descriptions of the following attributes:
 .sp
@@ -301,13 +285,12 @@ Architecture	SPARC, x86, PCI-based systems
 .TE
 
 .SH SEE ALSO
-.sp
 .LP
 \fBcdrw\fR(1), \fBeject\fR(1), \fBrmformat\fR(1), \fBrmmount\fR(1),
 \fBcfgadm_scsi\fR(1M), \fBcfgadm_usb\fR(1M), \fBfdisk\fR(1M), \fBmount\fR(1M),
-\fBumount\fR(1M), \fBdtfile.1X\fR (in CDE man pages), \fBlibusb\fR(3LIB),
+\fBumount\fR(1M),
 \fBscsi\fR(4), \fBvfstab\fR(4), \fBattributes\fR(5),
-\fBieee1394\fR(7D)\fBsd\fR(7D), \fBst\fR(7D), \fBugen\fR(7D), \fBusba\fR(7D),
+\fBieee1394\fR(7D), \fBsd\fR(7D), \fBst\fR(7D), \fBugen\fR(7D), \fBusba\fR(7D),
 \fBpcfs\fR(7FS), \fBcdio\fR(7I), \fBdkio\fR(7I)
 .sp
 .LP
@@ -317,9 +300,6 @@ Architecture	SPARC, x86, PCI-based systems
 \fISystem Administration Guide, Volume I\fR
 .sp
 .LP
-\fISolaris Common Desktop Environment: User's Guide\fR
-.sp
-.LP
 \fIUniversal Serial Bus Specification 2.0\fR
 .sp
 .LP
@@ -343,12 +323,8 @@ SCSI Specification \fIT10/995D Revision 11a\fR \(em March 1997
 SCSI Specification\fIT10/1236-D Revision 20\fR \(em July 2001
 .sp
 .LP
-SCSI Specification\fIT10/1416-D Revision 23\fR\(em May 2005
-.sp
-.LP
-http://\fIwww.sun.com/io\fR
+SCSI Specification\fIT10/1416-D Revision 23\fR \(em May 2005
 .SH DIAGNOSTICS
-.sp
 .LP
 Refer to \fBsd\fR(7D) and \fBst\fR(7D).
 .sp
@@ -475,7 +451,6 @@ USB mass storage devices.
 .RE
 
 .SH NOTES
-.sp
 .LP
 The Zip 100 drive does not comply with \fIUniversal Serial Bus Specification
 1.0\fR and cannot be power managed. Power Management support for Zip 100 has
@@ -502,17 +477,13 @@ some other USB device will also fail. To successfully remove a USB mass-storage
 device you must "close" all references to it.
 .sp
 .LP
-An Iomega Zip 100Mb disk cannot be formatted on an Iomega Zip250 drive. See the
-Iomega web site at \fIhttp://www.iomega.com\fR for details.
-.sp
-.LP
 Concurrent I/O to devices with multiple LUNs on the same device is not
 supported.
 .sp
 .LP
 Some USB CD-RW devices may perform inadequately at their advertised speeds. To
 compensate, use USB CD-RW devices at lower speeds (2X versus 4X). See
-\fBcdrw(1)\fR for details.
+\fBcdrw\fR(1) for details.
 .sp
 .LP
 This driver also supports CBI devices that do not use USB interrupt pipe for