projects / unix-history / blame
| Commit | Line | Data |
|---|---|---|
| 22c961eb RG |
1 | .Dd August 27, 1993 |
| 2 | .Dt SU 4 | |
| 3 | .Os 386BSD/NetBSD | |
| 4 | .Sh NAME | |
| 5 | .Nm su | |
| 6 | .Nd scsi user-level driver | |
| 7 | .Sh SYNOPSIS | |
| 8 | .Nm device-driver su | |
| 9 | .Sh DESCRIPTION | |
| 10 | The | |
| 11 | .Xr su | |
| 12 | driver provides support for a | |
| 13 | process to address arbitrary locations on the scsi bus. Minor | |
| 14 | numbers are mapped 1:1 to bus:target:lun. The lowest three bits being LUN | |
| 15 | and the next three bits being TARGET. Remaining bits are the bus number. | |
| 16 | .Pp | |
| 17 | A scsi adapter must also be separatly configured into the system | |
| 18 | before this driver makes sense. | |
| 19 | .Pp | |
| 20 | .Sh THE SU DEVICE IS NOT COMPLETED YET | |
| 21 | .Sh KERNEL CONFIGURATION | |
| 22 | There are no configuration parameters for the su option. It'e either there | |
| 23 | or it's not. | |
| 24 | ||
| 25 | .Pp | |
| 26 | .Sh IOCTLS | |
| 27 | The | |
| 28 | .Nm | |
| 29 | driver has no ioctls of it's own but rather acts as a medium for the | |
| 30 | generic | |
| 31 | .Xr scsi 4 | |
| 32 | ioctls. These are described in | |
| 33 | .Em sys/scsiio.h. | |
| 34 | ||
| 35 | ||
| 36 | .Sh FILES | |
| 37 | .Bl -tag -width /dev/su0-0-0XXXXXXXXXXX -compact | |
| 38 | .It Pa /dev/su[0-9]-[0-7]-[0-7] | |
| 39 | su{x}-{y}-{z} is the su device for the device at bus x, target y, lun z | |
| 40 | .El | |
| 41 | .Sh DIAGNOSTICS | |
| 42 | All | |
| 43 | .Xr scsi 4 | |
| 44 | debug ioclts work on | |
| 45 | .Nm | |
| 46 | devices. | |
| 47 | .Sh SEE ALSO | |
| 48 | .Xr sd 4 | |
| 49 | .Xr st 4 | |
| 50 | .Xr cd 4 | |
| 51 | .Xr uk 4 | |
| 52 | .Xr scsi 4 | |
| 53 | .Sh HISTORY | |
| 54 | The | |
| 55 | .Nm | |
| 56 | driver appeared in 386BSD 0.1 | |
| 57 |