summaryrefslogtreecommitdiffstats
path: root/share/man
diff options
context:
space:
mode:
authordufault <dufault@FreeBSD.org>1995-03-01 22:32:38 +0000
committerdufault <dufault@FreeBSD.org>1995-03-01 22:32:38 +0000
commit466baaef08335b4fb3b94989861766f7fbe3146f (patch)
treefb8419a27c82eeace1135b13924f0435f86e1940 /share/man
parent734069d1bb47d66aa9b2be03a9152402ac6851bb (diff)
downloadFreeBSD-src-466baaef08335b4fb3b94989861766f7fbe3146f.zip
FreeBSD-src-466baaef08335b4fb3b94989861766f7fbe3146f.tar.gz
Updated man pages to reflect new configuration options. These man pages
are getting pretty out of date and need to be visited some more.
Diffstat (limited to 'share/man')
-rw-r--r--share/man/man4/cd.411
-rw-r--r--share/man/man4/ch.411
-rw-r--r--share/man/man4/da.411
-rw-r--r--share/man/man4/sa.415
-rw-r--r--share/man/man4/scsi.452
-rw-r--r--share/man/man4/sd.411
-rw-r--r--share/man/man4/st.415
-rw-r--r--share/man/man4/uk.417
8 files changed, 107 insertions, 36 deletions
diff --git a/share/man/man4/cd.4 b/share/man/man4/cd.4
index 9b2bc71..63fb60e 100644
--- a/share/man/man4/cd.4
+++ b/share/man/man4/cd.4
@@ -5,8 +5,8 @@
.Nm cd
.Nd scsi cdrom driver
.Sh SYNOPSIS
-.Nm device-driver cd
-.Op Ar count
+.Nm device cd
+.Nm device cd1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr cd
@@ -51,11 +51,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Readonly'
type devices will be 'attached' to the
.Nm
-driver. The first found will be attached as
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
.Em cd0
and the next,
.Em cd1
etc.
+Beginning in 2.1 it is possible to specify what cd unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
The system utility
.Xr disklabel 1
diff --git a/share/man/man4/ch.4 b/share/man/man4/ch.4
index 472c68b..573d3b2 100644
--- a/share/man/man4/ch.4
+++ b/share/man/man4/ch.4
@@ -5,8 +5,8 @@
.Nm ch
.Nd scsi media-changer (juke box) driver
.Sh SYNOPSIS
-.Nm device-driver ch
-.Op Ar count
+.Nm device ch
+.Nm device ch1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr ch
@@ -23,11 +23,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Changer'
type devices will be 'attached' to the
.Nm
-driver. The first found will be attached as
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
.Em ch0
and the next,
.Em ch1
etc.
+Beginning in 2.1 it is possible to specify what ch unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
.Sh KERNEL CONFIGURATION
diff --git a/share/man/man4/da.4 b/share/man/man4/da.4
index a3face5..6b18286 100644
--- a/share/man/man4/da.4
+++ b/share/man/man4/da.4
@@ -5,8 +5,8 @@
.Nm sd
.Nd scsi disk driver
.Sh SYNOPSIS
-.Nm device-driver sd
-.Op Ar count
+.Nm disk sd
+.Nm disk sd1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr sd
@@ -46,11 +46,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Direct'
type devices will be 'attached' to the
.Nm
-driver. The first found will be attached as
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
.Em sd0
and the next,
.Em sd1
etc.
+Beginning in 2.1 it is possible to specify what sd unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
.Sh PARTITIONING
The
diff --git a/share/man/man4/sa.4 b/share/man/man4/sa.4
index 28f232b..c4b3872 100644
--- a/share/man/man4/sa.4
+++ b/share/man/man4/sa.4
@@ -5,8 +5,8 @@
.Nm st
.Nd scsi tape driver
.Sh SYNOPSIS
-.Nm device-driver st
-.Op Ar count
+.Nm tape st
+.Nm device st1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr st
@@ -46,11 +46,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Sequential'
type devices will be attached to the
.Nm
-driver. The first found will be attached as
-.Em st0
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
+.Em cd0
and the next,
-.Em st1
+.Em cd1
etc.
+Beginning in 2.1 it is possible to specify what cd unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
.Sh MOUNT SESSIONS
The
diff --git a/share/man/man4/scsi.4 b/share/man/man4/scsi.4
index b6d3995..d38cdd3 100644
--- a/share/man/man4/scsi.4
+++ b/share/man/man4/scsi.4
@@ -5,29 +5,61 @@
.Nm scsi
.Nd scsi system
.Sh SYNOPSIS
-.Nm device-driver scbus
+.Nm controller scbus0
+.Nm device cd0
+.Nm device ch0
+.Nm disk sd0
+.Nm tape st0
+.Nm device ch1 at scbus0 target 4 unit 0
.Sh DESCRIPTION
The
.Em scsi
-system provides a uniform and modular system for the implimentation
+system provides a uniform and modular system for the implementation
of drivers to control various scsi devices, and to utilise different
-scsi adapters through adapter drivers. When the system probes the
+scsi host adapters through host adapter drivers. When the system probes the
.Em SCSI
busses, it attaches any devices it finds to the appropriate
-drivers. If no driver seems appropriate, then at attaches the device to the
-uk (unknown) driver (if configured), so that user level scsi ioctls may
+drivers. If no driver seems appropriate, then it attaches the device to the
+uk (unknown) driver so that user level scsi ioctls may
still be performed against the device.
.Sh KERNEL CONFIGURATION
-Continuously changing. check your nearest bsd mailing list.
The option SCSIDEBUG enables the debug ioctl.
+.Pp
+All devices and the SCSI busses support boot time allocation so that
+an upper number of devices and controllers does not need to be configured;
+.Em "device sd0"
+will suffice for any number of disk drivers.
+.Pp
+The devices are either
+.Em wired
+so they appear as a particular device unit or
+.Em counted
+so that they appear as the next available unused unit.
+.Pp
+To configure a driver in the kernel without wiring down the device use a
+config line similar to
+.Em "device ch0"
+to include the changer driver.
+.Pp
+To wire down a
+unit use a config line similar to
+.Em "device ch1 at scbus0 target 4 unit 0"
+to assign changer 1 as the changer with SCSI ID 4 SCSI logical unit 0 on
+SCSI bus 0.
+.Pp
+When you have a mixture of wired down and counted devices then the
+counting begins with the first non-wired down unit for a particular
+type. That is, if you have a disk wired down as
+.Em "disk sd1" ,
+then the first non-wired disk shall come on line as
+.Em sd2 .
.Sh IOCTLS
-There are a number of ioctls that will (when the next stage is complete)
-work on any
+There are a number of ioctls that work on any
.Em SCSI
device. They are defined in
.Em sys/scsiio.h
-and can be applied against any scsi device that allows both read and write,
-though for devices such as tape, it must be applied against the control
+and can be applied against any scsi device that permits them.
+For the tape, it must be applied against the control
device. See the manual page for each device type for more information about
how generic scsi ioctls may be applied to a specific device.
.Bl -tag -width DIOCSDINFO____
diff --git a/share/man/man4/sd.4 b/share/man/man4/sd.4
index a3face5..6b18286 100644
--- a/share/man/man4/sd.4
+++ b/share/man/man4/sd.4
@@ -5,8 +5,8 @@
.Nm sd
.Nd scsi disk driver
.Sh SYNOPSIS
-.Nm device-driver sd
-.Op Ar count
+.Nm disk sd
+.Nm disk sd1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr sd
@@ -46,11 +46,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Direct'
type devices will be 'attached' to the
.Nm
-driver. The first found will be attached as
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
.Em sd0
and the next,
.Em sd1
etc.
+Beginning in 2.1 it is possible to specify what sd unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
.Sh PARTITIONING
The
diff --git a/share/man/man4/st.4 b/share/man/man4/st.4
index 28f232b..c4b3872 100644
--- a/share/man/man4/st.4
+++ b/share/man/man4/st.4
@@ -5,8 +5,8 @@
.Nm st
.Nd scsi tape driver
.Sh SYNOPSIS
-.Nm device-driver st
-.Op Ar count
+.Nm tape st
+.Nm device st1 target 4 lun 0
.Sh DESCRIPTION
The
.Xr st
@@ -46,11 +46,16 @@ As the scsi adapter is probed during boot, the
bus is scanned for devices. Any devices found which answer as 'Sequential'
type devices will be attached to the
.Nm
-driver. The first found will be attached as
-.Em st0
+driver.
+In FreeBSD releases prior to 2.1, the first found will be attached as
+.Em cd0
and the next,
-.Em st1
+.Em cd1
etc.
+Beginning in 2.1 it is possible to specify what cd unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
.Pp
.Sh MOUNT SESSIONS
The
diff --git a/share/man/man4/uk.4 b/share/man/man4/uk.4
index bf874e0..e0d8eff 100644
--- a/share/man/man4/uk.4
+++ b/share/man/man4/uk.4
@@ -5,17 +5,26 @@
.Nm uk
.Nd scsi user-level driver
.Sh SYNOPSIS
-.Nm device-driver uk
+.Nm device uk
.Sh DESCRIPTION
The
.Xr uk
driver provides support for a
process to address devices on the scsi bus for which there is no configured
driver.
-.Nm
-devices are numbered in the order they are found.
.Pp
-A scsi adapter must also be separatly configured into the system
+In FreeBSD releases prior to 2.1, the first unknown device
+found will be attached as
+.Em uk0
+and the next,
+.Em uk1
+etc.
+Beginning in 2.1 it is possible to specify what uk unit a device should
+come on line as; refer to
+.Xr scsi 4
+for details on kernel configuration.
+.Pp
+A scsi adapter must also be separately configured into the system
before this driver makes sense.
.Pp
.Sh KERNEL CONFIGURATION
OpenPOWER on IntegriCloud