|
|
|
scsi_disk(7) -- SCSI direct access device driver (sdisk)
|
|
This section describes the interface for access of SCSI disk, CD-ROM, and optical disk devices through the character special device driver. SCSI direct access devices store a sequence of data blocks. Each direct access device has a specific device size consisting of a number of data blocks and a logical block size. All data blocks have the same logical block size. Since I/O operations must have a ... |
|
scsi_tape(7) -- SCSI sequential access (tape) device driver
|
|
SCSI sequential-access (tape) devices store a sequence of data blocks. Data can be read and written using either fixed or variable sized block mode. If supported by the device, variable sized block mode is normally used (even when all blocks are the same size). Fixed sized block mode is generally only used for tape devices which do not support variable sized blocks. Fixed sized block mode can be u... |
|
|
sioc_io(7) -- SCSI pass-through interface
|
|
SCSI devices are controlled by a device-specific driver, when one exists. Device-specific drivers, such as those for SCSI direct access (disk) and sequential access (tape) devices, coordinate device and driver states to accomplish correct logical device behavior. The sioc_io pass-through interface enables the use of SCSI devices and commands not normally supported by these device-specific drivers.... |
|
slp_syntax(7) -- SLP Service Type Syntax
|
|
The SLP API expects service type information to be passed while querying for SLP service information and also while registering and deregistering services. The SLP API accepts service type information in URL format also. The service type string contains the following information. Name of the service type. Naming Authority responsible for the service name. The service type string is of the form: se... |
|
socket(7) -- interprocess communications
|
|
Sockets are communication endpoints that allow processes to communicate either locally or remotely. They are accessed by means of a set of system calls (see socket(2)). The following ioctl() requests are defined in (see ioctl(2)): FIOSNBIO If the int with the address arg is non-zero, the socket is put into non-blocking mode. Otherwise, the socket is put into blocking mode. Blocking m... |
|
streamio(7) -- STREAMS ioctl commands
|
|
STREAMS ioctl commands are a subset of the ioctl() system calls which perform a variety of control functions on streams. fildes is an open file descriptor that refers to a stream. command determines the control function to be performed as described below. arg represents additional information that is needed by this command. The type of arg depends upon the command, but it is generally an integer o... |
|
strlog(7) -- STREAMS log driver
|
|
The STREAMS log driver allows user-level processes and STREAMS drivers and modules to perform error logging and event tracing. These tasks are done via a user interface and a kernel interface. Further, the STREAMS log driver delivers error logging and event tracing messages to the Network Tracing and Logging Facility (NetTL) (see nettl(1M), netfmt(1M), and nettlconf(1M)). The interface that this d... |
|
stty(7) -- terminal interface for Version 6/PWB compatibility
|
|
These routines attempt to map the UNIX Time-Sharing System, Sixth Edition (Version 6), and PWB stty and gtty calls into the current ioctls that perform the same functions. The mapping cannot be perfect. The way the features are translated is described below. The reader should be familiar with termio(7) before studying this entry. The following data structure is defined in the include file |
|
sttyv6(7) -- terminal interface for Version 6/PWB compatibility
|
|
These routines attempt to map the UNIX Time-Sharing System, Sixth Edition (Version 6), and PWB stty and gtty calls into the current ioctls that perform the same functions. The mapping cannot be perfect. The way the features are translated is described below. The reader should be familiar with termio(7) before studying this entry. The following data structure is defined in the include file |
|
sttyV6(7) -- terminal interface for Version 6/PWB compatibility
|
|
These routines attempt to map the UNIX Time-Sharing System, Sixth Edition (Version 6), and PWB stty and gtty calls into the current ioctls that perform the same functions. The mapping cannot be perfect. The way the features are translated is described below. The reader should be familiar with termio(7) before studying this entry. The following data structure is defined in the include file |
|
syscon(7) -- system console interface
|
|
/dev/console provides a termio interface to the device configured as the system console. The init(1M) man page discusses the uses of /dev/systty and /dev/syscon. Output data normally sent to the console, either through /dev/console or generated by a kernel printf, may be redirected to another terminal or pseudo-terminal device through the TIOCCONS ioctl(). See termio(7) for details. |
|
systty(7) -- system console interface
|
|
/dev/console provides a termio interface to the device configured as the system console. The init(1M) man page discusses the uses of /dev/systty and /dev/syscon. Output data normally sent to the console, either through /dev/console or generated by a kernel printf, may be redirected to another terminal or pseudo-terminal device through the TIOCCONS ioctl(). See termio(7) for details. |
|
telm(7) -- STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respective
|
|
A Telnet pseudo-terminal consists of a tightly-coupled pair of character devices, called the master device and slave device. The master and slave device drivers work together to provide a Telnet connection on the server side where the master provides a connection to telnetd and the slave provides a terminal device special file access for the Telnet application processes, as depicted below: -------... |
|
tels(7) -- STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respective
|
|
A Telnet pseudo-terminal consists of a tightly-coupled pair of character devices, called the master device and slave device. The master and slave device drivers work together to provide a Telnet connection on the server side where the master provides a connection to telnetd and the slave provides a terminal device special file access for the Telnet application processes, as depicted below: -------... |
|
termio(7) -- general terminal interface
|
|
All HP-UX asynchronous communications ports use the same general interface, regardless of what hardware is involved. Network connections such as rlogin (see rlogin(1) use the pseudo-terminal interface (see pty(7). This discussion centers around the common features of this interface. |
