|
|
|
autochanger(7) -- SCSI interfaces for medium changer device and magnetooptical autochanger surface device
|
|
An autochanger is a SCSI mass storage device, consisting of a mechanical changer device, one or more data transfer devices (such as optical disk drives), and media (such as optical disks) for data storage. The mechanical changer moves media between storage and usage locations within the autochanger. Depending on system architecture, one of two medium changer drivers (schgr or autox0) provides acce... |
|
blmode(7) -- terminal block mode interface
|
|
This terminal interface adds functionality to the current termio(7) functionality to allow for efficient emulation of MPE terminal driver functionality. Most importantly, it adds the necessary functionality to support block mode transfers with HP terminals. The block mode interface only affects input processing and does not affect write requests. Write requests are always processed as described in... |
|
|
cent(7) -- Centronics-compatible interface
|
|
cent is a simple, widely used communication protocol most commonly associated with printers, plotters and scanners. It is an eight-bit parallel data interface with additional control signals from the host computer, and status signals from the peripheral. The cent interface driver does no character processing; that is, it does not interpret the data being transferred between computer and peripheral... |
|
clone(7) -- opens a major and minor device pair on a STREAMS driver
|
|
The clone driver is a "pass through" device driver that allows other drivers to select unique minor device numbers on each open(). In effect, the driver passes an open operation through to the other driver. This mechanism allows for multiple instantiations of a driver, each with a different minor number, through a single device file. When the clone driver is opened, it is passed a major and mino... |
|
console(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. |
|
ddfa(7) -- Data Communications and Terminal Controller (DTC) Device File Access (DDFA) software
|
|
The Data Communications and Terminal Controller (DTC) Device File Access (DDFA) software allows access from HP-UX system utilities and user applications to terminal servers using standard HP-UX structures. DDFA provides an interface to remote LAN-connected terminal server ports that is similar to the interface for local directly-connected ports. The basic principle is that a daemon is created for ... |
|
diag0(7) -- diagnostic interface to HP-PB I/O subsystem
|
|
diag0 is a diagnostic pseudo-driver, which provides HP support tools with access to the HP-PB I/O subsystem. This driver is used by hardware monitors and tools within the Support Tools Manager (STM), to interact with peripherals connected to the system via HP-PB. The I/O drivers also send diagnostic events to diag0 for diagnostic logging by the Support Tools Manager. Without diag0, information tha... |
|
diag1(7) -- diagnostic interface to the PCI I/O subsystem
|
|
diag1 is a diagnostic pseudo-driver, which provides support tools with access to the PCI I/O subsystem. This driver is used by tools within the Support Tools Manager (STM) to interact with PCI cards connected to the system. Without diag1, support tools for PCI cards will not be able to operate. |
|
diag2(7) -- interface for diagnostic logging and interface to processors
|
|
diag2 is used by hardware monitors and tools within the Support Tools Manager (STM), to interact with processor hardware via Processor Dependent Code (PDC). Without diag2, support tools for processors will not be able to operate. diag2 is also the key component for the following support features: I/O error logging Low priority machine check (LPMC) logging Memory error logging Pro-active memory pag... |
|
disk(7) -- direct disk access
|
|
This entry describes the actions of HP-UX disk drivers when referring to a disk as either a block-special or character-special (raw) device. |
|
dlpi(7) -- data link provider interface
|
|
This manual page gives a brief description on DLPI (the data link provider interface) and how to interface with the set of API's that are provided by DLPI. HP-UX DLPI serves as a Layer 2 (Data Link Layer) of an OSI architecture. DLPI serves as an interface between LAN device drivers and DLPI users. DLPI is intended for use by experienced network users only. HP-UX DLPI has two broader sets of inte... |
|
floppy(7) -- direct flexible or ``floppy'' disk access
|
|
Flexible disk devices are removable-media disk devices that are typically used to share data with other systems. Media types are identified by physical size (such as 3.5-inch and 5.25-inch), number of data surfaces (or sides), and data density. By convention, flexible disk devices are named using the same conventions as those used for other disk devices (see disk(7)). Data can be stored on flexibl... |
|
framebuf(7) -- information for raster frame-buffer devices
|
|
Frame-buffer devices are raster-based displays. These devices use memory-mapped I/O to obtain much higher performance than possible with tty-based graphic terminals. Frame-buffer devices can be accessed directly using this interface, although access through the STARBASE libraries is recommended (see starbase(3G)). Direct access to framebuffer devices entails precise knowledge of the frame-buffer a... |
|
gang_sched(7) -- Gang Scheduler
|
|
The gang scheduler permits a set of MPI (Message Passing Interface) processes, or multiple threads from a single process, to be scheduled concurrently as a group. Gang scheduling is enabled and disabled by setting the MP_GANG environment variable to ON or OFF. The gang scheduling feature can significantly improve parallel application performance in loaded timeshare environments that are oversubscr... |
|
hil(7) -- HP-HIL device driver
|
|
HP-HIL, the Hewlett-Packard Human Interface Link, is the HewlettPackard standard for interfacing a personal computer, terminal, or workstation to its input devices. hil supports devices such as keyboards, mice, control knobs, ID modules, button boxes, digitizers, quadrature devices, bar code readers, and touchscreens. On systems with a single link, HP-HIL device file names use the following format... |
|
hilkbd(7) -- HP-HIL mapped keyboard driver
|
|
HP-HIL, the Hewlett-Packard Human Interface Link, is the HewlettPackard standard for interfacing a personal computer, terminal, or workstation to its input devices. hilkbd supplies input from all mapped keyboards on a specified HP-HIL link. hilkbd returns mapped keycodes, not ASCII characters. ``Raw'' keycodes are the individual key downstrokes and upstrokes, and are different for each type of k... |
|
intro(7) -- introduction to device special files
|
|
This section describes the device special files used to access HP peripherals and device drivers. The names of the entries are generally derived from the type of device being described (disk, terminal, etc.), not the names of the device special files or device drivers themselves. Characteristics of both the hardware device and the corresponding HP-UX device driver are discussed where applicable. T... |
|
iomap(7) -- physical I/O address mapping
|
|
The iomap mechanism allows the mapping (thus direct access) of physical I/O addresses into the user process address space. For PARISC machines, the physical I/O address space begins at 0xf0000000 and extends to 0xffffffff. The special (device) files for iomap devices are character special files using the dynamic major number allocation scheme. The minor number for iomap devices is of the form: 0xA... |
|
ipmi(7) -- intelligent platform management interface (IPMI) driver
|
|
The /dev/ipmi driver allows user processes to send IPMI messages to the BMC (Baseboard Management Controller) System Message Interface. The following data structures are provided in the header file for sending IPMI requests to the BMC. |
|
kmem(7) -- perform I/O on kernel memory based on symbol name.
|
|
When used with a valid file descriptor for /dev/kmem (kmemfd), ioctl can be used to manipulate kernel memory. The specifics of this manipulation depend on the command given as follows: MIOC_READKSYM Read mirk_buflen bytes of kernel memory starting at the address for mirk_symname into mirk_buf. rks is a pointer to a mioc_rksym structure, defined below. MIOC_IREADKSYM Indirect read. Read sizeof(void... |
|
lan(7) -- network I/O card access information
|
|
This manual entry gives a brief description on how to access the LAN device driver at Layer 2 (Data Link Layer) of the OSI architecture. The LAN device driver controls the various LAN interface cards (e.g, Ethernet/IEEE 802.3, FDDI, Token Ring) at Layer 1 (Physical Layer). The Data Link Provider Interface (DLPI) is the supported method for accessing the LAN device driver at Layer 2. DLPI is intend... |
|
ldterm(7) -- standard STREAMS terminal line discipline module
|
|
ldterm is a STREAMS module that supplies the line discipline for streams-based terminal or pseudo-terminal device drivers. This module provides most of the functions of the general terminal interface described in termio(7). However, it does not perform the low-level device control functions specified by the c_cflag word defined by the POSIX termios structure or the System V termio structure (defin... |
|
lp(7) -- line printer
|
|
This section describes capabilities provided by many line printers supported by various versions of the HP-UX operating system. A line printer is a character special device that may optionally have an interpretation applied to the data. If the character special device file has been created with the raw option (see the HP-UX System Administrator manuals for information about creating device files w... |
|
lvm(7) -- Logical Volume Manager (LVM)
|
|
The Logical Volume Manager (LVM) is a subsystem for managing disk space. The HP LVM subsystem offers value-added features, such as mirroring (with the optional HP MirrorDisk/UX software), high availability (with the optional HP ServiceGuard software), and striping, that enhance availability and performance. Unlike earlier arrangements where disks were divided into fixed-sized sections, LVM allows ... |
|
mem(7) -- main memory
|
|
mem is a special file that is an image of the main memory of the computer. It may be used, for example, to examine and patch the system. Byte addresses in mem are interpreted as physical memory addresses. References to non-existent locations cause errors to be returned. File kmem is the same as mem except that kernel virtual memory rather than physical memory is accessed. Please refer to kmem(7) f... |
|
modem(7) -- asynchronous serial modem line control
|
|
This section describes the two modes of modem line control and the three types of terminal port access. It also discusses the effect of the bits of the termio structure that affect modem line control. The modem related ioctl(2) system calls are discussed at the end of the document. |
|
mt(7) -- magnetic tape interface and controls for stape and tape2
|
|
This entry describes the behavior of HP magnetic tape interfaces and controls, including reel-to-reel, DDS, QIC, 8mm, and 3480 tape drives. The files /dev/rmt/* refer to specific raw tape drives, and the behavior of each given unit is specified in the major and minor numbers of the device special file. |
|
nfs(7) -- network file system
|
|
The Network File System (NFS) allows a client node to perform transparent file access over the network. By using NFS, a client node operates on files residing on a variety of servers and server architectures, and across a variety of operating systems. File access calls on the client (such as read requests) are converted to NFS protocol requests and sent to the server system over the network. The s... |
|
null(7) -- null file
|
|
Data written on a null special file is discarded. Reads from a null special file always return 0 bytes. |
|
pckt(7) -- Packet Mode module for STREAMS pty (pseudo-terminal)
|
|
The Packet Mode feature for STREAMS pty devices allows the user process on the master side of the pty device to be informed of state changes in the pty. To enable Packet Mode in the STREAMS pty device, the user process must push the pckt module onto the master side of the pty with a call to the STREAMS I_PUSH ioctl(2) system call. When the pckt module is pushed onto a STREAMS pty master, certain S... |
|
pfto(7) -- Powerfail Timeout
|
|
HP-UX SCSI disk device drivers have a timeout facility that detects non-responding disks. VxVM uses this mechanism in its Powerfail Timeout (pfto) feature. You can specify a timeout value for individual VxVM disks using the vxdisk command (see the EXAMPLES section below). If a disk fails to respond in the specified timeout period, the driver receives a timer interrupt. pfto values are persistent a... |
|
poll(7) -- monitor I/O conditions on multiple file descriptors
|
|
/dev/poll provides an interface to the event port driver allowing a user to synchronously monitor a specific set of conditions associated with a registered set of file descriptors. Poll conditions include the ability to read or write data without blocking and certain exceptional conditions. Access to /dev/poll is provided through the open(), write(), and ioctl() system calls. The /dev/poll event p... |
|
ps2(7) -- PS/2 keyboard/mouse device driver and files
|
|
The ps2 driver allows the use of IBM Personal System/2 (PS/2) compatible keyboards and mouse devices on Hewlett-Packard workstations equipped with PS/2 interface hardware. On systems with a single interface, PS/2 device file names use the following format: /dev/ps2_n where n where n represents the interface port number, ranging from 0 to 15. For example, the device file /dev/ps2_1 is used to acces... |
|
ps2kbd(7) -- PS/2 keyboard/mouse device driver and files
|
|
The ps2 driver allows the use of IBM Personal System/2 (PS/2) compatible keyboards and mouse devices on Hewlett-Packard workstations equipped with PS/2 interface hardware. On systems with a single interface, PS/2 device file names use the following format: /dev/ps2_n where n where n represents the interface port number, ranging from 0 to 15. For example, the device file /dev/ps2_1 is used to acces... |
|
ps2mouse(7) -- PS/2 keyboard/mouse device driver and files
|
|
The ps2 driver allows the use of IBM Personal System/2 (PS/2) compatible keyboards and mouse devices on Hewlett-Packard workstations equipped with PS/2 interface hardware. On systems with a single interface, PS/2 device file names use the following format: /dev/ps2_n where n where n represents the interface port number, ranging from 0 to 15. For example, the device file /dev/ps2_1 is used to acces... |
|
ptem(7) -- STREAMS pty (pesudo-terminal) Emulation module
|
|
ptem is a STREAMS module that emulates a terminal when used in conjunction with ldterm (STREAMS line discipline) and pts (STREAMS slave pty driver). The ptem module normally sits above pts and below ldterm. The user process must push the ptem module onto the slave side of the pty with a call to the STREAMS I_PUSH ioctl(2) system call before ldterm is pushed. ptem is responsible for processing all ... |
|
ptm(7) -- STREAMS master pty (pseudo-terminal) driver
|
|
A pseudo-terminal (pty) consists of a tightly-coupled pair of character devices, called the master device and slave device. The pty master and slave device drivers work together to simulate a terminal connection where the master provides a connection to the pseudo terminal server process and the slave provides a terminal device special file access for the terminal application processes, as depicte... |
|
pts(7) -- STREAMS slave pty (pseudo-terminal) driver
|
|
A pseudo-terminal (pty) consists of a tightly-coupled pair of character devices, called the master device and slave device. The pty master and slave device drivers work together to simulate a terminal connection where the master provides a connection to the pseudo terminal server process and the slave provides a terminal device special file access for the terminal application processes, as depicte... |
|
pty(7) -- pseudo terminal driver
|
|
The pty driver provides support for a device-pair termed a pseudo terminal. A pseudo terminal is a pair of character devices, a master device and a slave device. The slave device provides to application processes an interface identical to that described in termio(7). Unlike all other devices that provide the interface described in termio(7), the slave device does not have a hardware device behind ... |
|
random(7) -- strong random number generator
|
|
The character special files /dev/random and /dev/urandom provide an interface to the kernel-resident random number generator, rng. A read() from /dev/random is potentially blocking, as compared to a read from /dev/urandom which is always nonblocking. Data from /dev/urandom can potentially have lower entropy than data from /dev/random. The rng module is a dynamically loadable kernel module (DLKM). ... |
|
rng(7) -- strong random number generator
|
|
The character special files /dev/random and /dev/urandom provide an interface to the kernel-resident random number generator, rng. A read() from /dev/random is potentially blocking, as compared to a read from /dev/urandom which is always nonblocking. Data from /dev/urandom can potentially have lower entropy than data from /dev/random. The rng module is a dynamically loadable kernel module (DLKM). ... |
|
routing(7) -- system support for local network packet routing
|
|
The network facilities for HP-UX provide general packet routing support. Routing table maintenance is handled by application processes. A routing table consists of a set of data structures used by the network facilities to select the appropriate remote host or gateway when transmitting packets. The table contains a single entry for each route to a specific network or host, as displayed by the nets... |
|
sad(7) -- STREAMS Administrative Driver
|
|
The sad driver provides an interface to the autopush facility using the ioctl() function. As an interface, the sad driver enables administrative tasks to be performed on STREAMS modules and drivers. By specifying the command parameter to the ioctl() function, an administrator can configure autopush information for a device, get information on a device, or check a list of modules. fildes is a file ... |
|
scsi(7) -- Small Computer System Interface device drivers
|
|
The Small Computer System Interface (SCSI) is an American National Standard for interconnecting computers and peripheral devices. HP-UX supports the SCSI device protocol on parallel SCSI interfaces (see ANSI Std X3.131-199X, ``SCSI-3'') and Fibre Channel interfaces (see ANSI Std X3.269-199X, "Fibre Channel Protocol for SCSI"). The SCSI standard includes specifications for a variety of device t... |
|
scsi_ctl(7) -- SCSI pass-through driver
|
|
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 scsi_ctl pass-through driver enables use of SCSI devices and commands not normally supported by these device-specific drivers. Depen... |
|
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. |
|
termios(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. |
|
termiox(7) -- extended general terminal interface
|
|
The extended general terminal interface supplements the termio(7) general terminal interface by adding support for asynchronous hardware flow control and local implementations of additional asynchronous features. Some systems may not support all of these capabilities because of hardware or software limitations. Other systems may not permit certain functions to be disabled. In such cases, the appro... |
|
timod(7) -- STREAMS module for converting ioctl() calls into Transport Interface messages
|
|
The timod module is a STREAMS module that converts ioctl() calls from a transport user supporting the Transport Interface (TI) into messages that a transport protocol provider supporting TI can consume. This allows the user to initiate certain TI functions as atomic operations. This release of HP-UX no longer automatically pushes timod whenever a t_open(3) is performed. The TLI and XTI libraries h... |
|
tirdwr(7) -- STREAMS module for reads and writes by Transport Interface users
|
|
The tirdwr module is a STREAMS module that provides a transport user supporting the Transport Interface (TI) with an alternate interface to a transport protocol provider supporting TI. This alternate interface allows the transport user to communicate with the transport protocol provider using the read() and write() functions. It can also continue to use the putmsg() and getmsg() functions, but the... |
|
tty(7) -- controlling terminal interface
|
|
The file /dev/tty is, in each process, a synonym for the control terminal associated with the process group of that process, if any. It is useful for programs or shell sequences that need to be sure of writing messages on the terminal no matter how output has been redirected. It can also be used for programs that demand the name of a file for output, when typed output is desired and it is tiresome... |
|
urandom(7) -- strong random number generator
|
|
The character special files /dev/random and /dev/urandom provide an interface to the kernel-resident random number generator, rng. A read() from /dev/random is potentially blocking, as compared to a read from /dev/urandom which is always nonblocking. Data from /dev/urandom can potentially have lower entropy than data from /dev/random. The rng module is a dynamically loadable kernel module (DLKM). ... |
|
VLAN(7) -- virtual LANs (VLANs)
|
|
VLANs are logical, or "virtual," network segments that can span multiple physical network segments. A primary benefit of VLANs is that they can isolate broadcast and multicast traffic by determining which destinations should receive that traffic, thereby making better use of switch and end-station resources. The commands described here are for interactive administration of HPUX virtual LANs (VLA... |
|
vlan(7) -- virtual LANs (VLANs)
|
|
VLANs are logical, or "virtual," network segments that can span multiple physical network segments. A primary benefit of VLANs is that they can isolate broadcast and multicast traffic by determining which destinations should receive that traffic, thereby making better use of switch and end-station resources. The commands described here are for interactive administration of HPUX virtual LANs (VLA... |
|
vxconfig(7) -- VERITAS Volume Manager configuration device
|
|
The vxconfig device is the interface through which all changes to the volume driver state are performed in VERITAS Volume Mananger (VxVM). This device can only be opened by one process at a time. The initial volume configuration is downloaded into the kernel through this device. The vxconfigd process updates the configuration through this device. The vxconfigd process was designed to be the sole a... |
|
vxdmp(7) -- VERITAS Volume Manager multipathing disk devices
|
|
Multipathed disk devices in VERITAS Volume Manager (VxVM) represent virtual devices with one or more physical access paths to a physical disk. The Multipathing feature provides disk access reliability by dynamically switching to another physical path if there is a path failure. Every disk that is visible to VxVM is represented by a multipath device node in the /dev/vx/dmp and /dev/vx/rdmp director... |
|
vxfsio(7) -- VxFS file system control functions
|
|
The vxfs ioctl(2) enhancements provide for extended control over open files. The argument fildes is an open file descriptor. The data type and value of arg are specific to the type of command specified by cmd. Unless specified, arg is treated as an int type. The symbolic names for commands and file status flags are defined by the sys/fs/vx_ioctl.h header file. |
|
vxinfo(7) -- VERITAS Volume Manager general information device
|
|
The vxinfo device in VERITAS Volume Manager (VxVM) gathers performance statistics from the kernel for a supplied object. Statistics can be retrieved for volume, plex, subdisk, and disk media objects. Statistics can also be cleared through this interface. |
|
vxio(7) -- VERITAS Volume Manager virtual disk devices
|
|
Volume devices are the virtual disk devices in VERITAS Volume Manager (VxVM). The volume devices support a virtual disk access method with disk mirroring and disk striping. A volume is a logical entity composed of one or more plexes. A read can be satisfied from any plex, while a write is directed to all plexes. The virtual disk devices have a wide variety of behaviors, which are programmable thro... |
|
vxiod(7) -- VERITAS Volume Manager I/O daemon process control device
|
|
The vxiod device in VERITAS Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process context is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continuing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with ... |
|
vxtrace(7) -- VERITAS Volume Manager I/O Tracing Device
|
|
The vxtrace device implements the VERITAS Volume Manager (VxVM) I/O tracing and the error tracing. An I/O tracing interface is available that users or processes can use to get a trace of I/Os for specified sets of kernel objects. Each separate user of the I/O tracing interface can specify the set of desired trace data independent of all other users. I/O events include regular read and write operat... |
|
xopen_networking(7) -- X/Open Networking Interfaces
|
|
X/Open has defined XTI, Sockets, and IP Address Resolution interfaces in X/Open CAE Specification, Networking Services, Issue 4 (UNIX 95) and X/Open CAE Specification, Networking Services, Issue 5 (UNIX 98). For a detailed description of these interfaces, please refer to the above specifications or to the book Go Solo, which is published by Prentice Hall. Go Solo also includes a CD ROM which conta... |
|
zero(7) -- zero file
|
|
/dev/zero is a zero special file. Reads from a zero special file always return characters whose value is '0' (\0 characters). Data written on a zero special file is discarded or ignored. Seeks on a zero special file will always succeed. Private mmap() of a zero special file is allowed (see mmap(2)). Shared mmap() is not allowed. |
