|
|
|
alp(7) -- algorithm pool management module
|
|
/* * This is a SAMPLE module that registers with ALP and performs * a one-message delay. */ #include #include #include #include #include static mblk_t *dely(); caddr_t delyopen(); /* * Our state structure. Keeps its own address and a pointer. */ struct dstruct { caddr_t d_unique; mblk_t *d_mp; }; /* * The name is "Dely". It has an open routine "delyopen" * and an interface "dely". */ static struct algo delyalgo = { 0, (q... |
|
arp(7) -- Address Resolution Protocol
|
|
The following messages can appear on the console: arp: host with ether address %x:%x:%x:%x:%x:%x is using my IP address x.x.x.x ARP has discovered another host on the local network which responds to mapping requests for its own Internet address. arp: ether address is broadcast for IP address x.x.x.x ARP has discovered another host on the local network which maps that host's IP address onto the ethernet broadcast address.... |
|
|
ccsync(7) -- Power Fortran join accelerator.
|
|
This device is used by Power Fortran to speed up join synchronization. |
|
cdsio(7) -- 6-port serial I/O
|
|
6-port boards can be used for modems or other asynchronous, serial I/O devices. The ports provided by the cdsio board are very similar to the on-board duart ports. Various character echoing and interpreting parameters can be set independently for each port. See termio(7) for details. By opening either the ttyd*, ttym*, or ttyf* device name of a port, different hardware signals are supported. Ttyd* is typically used for direct connect devices such as terminals; ttym* is used for devices that use ... |
|
cl(7) -- CrayLink Driver
|
|
The cl module provides a raw device interface to XPC (cross partition communication). These devices take advantage of the XPC rendezvous capabilities to allow DMA transfers directly from the source to the destination without any intermediate copying if possible. The DMA operation is done using the BTE which supports transfers of multiple cache lines on cache line boundaries. Therefore, in order to avoid the overhead of the cl driver copying data to an intermediate buffer, the source ... |
|
clone(7) -- open any minor device on a STREAMS driver
|
|
Multiple opens of the same minor device cannot be done through the clone interface. Executing stat(2) on the filesystem node for a cloned device yields a different result from executing fstat(2) using a file descriptor obtained from opening the node. |
|
connld(7) -- line discipline for unique stream connections
|
|
streamio(7). PPPPaaaaggggeeee 2222 |
|
console(7) -- console interface
|
|
/dev/console |
|
cserialio(7) -- character driver interface to serial communication ports
|
|
On Origin, O2, Octane and Challenge/Onyx systems, the special files /dev/ttyc* provide a character based interface (as opposed to a streams based interface) to the system serial ports. The hardware accessed by each special file is determined by the portno portion of the pathname (see serial(7) for further details). The character based interface is intended to provide a low cost option for applications wishing to do bulk data transfer via the serial ports with no character interpretation. There i... |
|
db(7) -- local name service database
|
|
The db client library fetches name service data out of an db(3B) format database file on the local host. This library is meant to be used only by the nsd(1M) daemon to efficiently access local name service data. The library /var/ns/lib/libns_db.so is opened by the nsd(1M) daemon when db is listed as the protocol for some map in a nsswitch.conf file. The library contains code to fetch data from a local db file and present it as lines from the configuration file from which it came. The nsd daemon ... |
|
dksc(7) -- dksc (SCSI) disk driver
|
|
The dksc driver supports all disk types that use a SCSI command set. This includes traditional parallel SCSI as well as Fibre Channel Arbitrated Loop and Fibre Channel Fabric devices (devices connected through a Fibre Channel switch). Currently, 8 bit parallel SCSI (also called narrow SCSI) allows up to seven SCSI drives attached per SCSI bus, 16 bit parallel SCSI (also called wide SCSI) allows 15 drives. Fibre Channel Arbitrated Loop (FC-AL) allows up to 125 drives (some implementations limit t... |
|
dlpi(7) -- data link provider interface
|
|
A.) Snif master file and interfaces The DLPI includes three master files: /var/sysgen/master.d/llc2, /var/sysgen/master.d/xtimer, and /var/sysgen/master.d/snif. You should not need to change the llc2 master file and the xtimer master file. However, the snif master file provides a mapping between the minor number of an interface and its name. The snif master file shipped with the DLPI subsystem has three interfaces pre-defined: one Token Ring interface, one Ethernet interface, and one FDDI interf... |
|
dmrb(7) -- digital media ring buffer device
|
|
The Digital Media Ring Buffer device is used to manage continuous streams of data between cooperating user processes and between user processes and the kernel. The dmrb driver is intended to be used internally by various digital media libraries and has no direct user or programmer interfaces. PPPPaaaaggggeeee 1111 |
|
dns(7) -- Domain Name Service
|
|
The Domain Name System (DNS) is an Internet standard name service for hostname to address translation. Queries are made from a client library (termed the resolver(4)) to a server daemon named(1M). The daemon nsd(1M) will make these calls and present the data in a filesystem namespace when the dns keyword exists in the nsswitch.conf configuration file for a domain. This man page documents the behavior of the DNS extension to the nsd daemon. The nsd daemon reads all of the nsswitch.conf configurat... |
|
dn_ll(7) -- 4DDN special files
|
|
/dev/dn_ll /dev/dn_netman |
|
drain(7) -- capture unimplemented link-layer protocols
|
|
The Drain protocol provides non-promiscuous capture of packets having unimplemented link-layer protocol types, i.e., packets that the operating system normally receives and drops ``down the drain''. It treats packets as datagrams containing a link-layer header followed by data. Drain uses the Raw address format, interpreting ports as link-layer type codes (in host byte order) to match against unimplemented types in received packets. Multiple sockets may bind to the same port on a network inter... |
|
ds(7) -- generic (user mode) SCSI driver
|
|
The ds interface provides user-mode access to the SCSI bus. It supports the programming interfaces described in dslib(3) and below. All of the ds devices support the same general interface. The program calls open, gaining exclusive use of a specified SCSI device (that is, two processes may not both have the same device open at the same time via this driver). Additionally, when the O_EXCL open flag set, exclusive use of the target will be acquired. No other SCSI driver will be able to use the tar... |
|
duart(7) -- on-board serial ports
|
|
Each IRIS-4D system uses a DUART to connect the mouse and the keyboard. Most models are also equipped with some number of additional `on-board' serial ports. The Indigo, Indy, Indigo2, O2 and OCTANE have two ports; and the Onyx and the Challenge can be configured with as few as four serial ports and as many as 16. The first of these ports, /dev/ttyd1, is often used for the `serial' or `debugging' console. Other ports are commonly used for serial terminal connections, modems, a dial-and-button... |
|
eg(7) -- gigabit ethernet driver
|
|
/hw/net/egN special file |
|
ei(7) -- external interrupts interface
|
|
The special files in /dev/external_int provide access to the external interrupt interface on those machines which have such an interface. This interface allows separate machines to send and receive interrupts over a dedicated wire for purposes of inter-machine synchronization. Using this device, a user process may generate outgoing interrupts to other machines, or receive interrupts from other machines in a variety of ways: the user process may request to block in an ioctl() until an interrupt i... |
|
ethernet(7) -- Ethernet controllers
|
|
Various error messages are printed by the kernel when a problem is encountered. The message is preceded by the controller name, for example, et0. Serious errors are flagged with a dagger (-). If they occur repeatedly, contact your product support service for assistance. By default, many non-serious errors will not cause a diagnostic message to be displayed on the console. To enable all driver diag messages, use the command ifconfig xxx debug where xxx is the ethernet network interface name. The ... |
|
failover(7) -- disk device alternate path support
|
|
Failover creates an infrastructure for the definition and management of multiple paths to a single disk device or lun. This failover infrastructure is used by an SGI logical volume manager (XLV, XVM) to select the path used for access to the logical volume(s) created on the storage device(s). In the presense of i/o errors, the SGI logical volume manager will request from the failover infrastructure a new path to be used for access to the erring logical volumes. This path failover requires the lo... |
|
files(7) -- local files name service parser library
|
|
The files client library parses traditional local name service configuration files such as /etc/passwd and makes the data available through the nsd(1M) filesystem. This library is meant to be used only by the nsd(1M) daemon to efficiently access local name service data. The library /var/ns/lib/libns_files.so is opened by the nsd(1M) daemon when files is listed as the protocol for some map in a nsswitch.conf file. Extended attributes in the nsswitch.conf file can be used to control the behavior o... |
|
fsctl(7) -- operations on a mounted file system
|
|
fsctl presents a device interface for performing low-level operations on a mounted file system. This driver is used by the file system reorganizer, fsr. WARNING: this driver does NOT copy or otherwise operate on data within file system blocks. This can be done through the raw device interface to the file system. Only the superuser can open /dev/fsctl. Only one process at a time can open this device. The following operations are available as ioctl(2) calls on a file descriptor opened on this devi... |
|
genlock(7) -- genlock capability on IRIS-4D Series machines
|
|
In some multi-screen stereo applications it is desirable to genlock stereo screens together. Care must be taken to ensure that right-eye views are locked together. For some older stereo formats, this may require several attemps; the system may lock the left eye of one screen to the right eye of the other. If this occurs, turn genlock off and try the genlock again. Removing and reconnecting the sync signal from the sync input is not suggested, as this may cause problems with the hardware. Genlock... |
|
gse(7) -- Silicon Graphics 5080 workstation interface card
|
|
/dev/gse |
|
gvo(7) -- Serial digital video option for Onyx InfiniteReality graphics
|
|
In low-latency mode, a suitable genlock signal must be supplied, or the GVO will not function correctly. in low-bandwidth mode, the source channel must have a frame rate that is faster than the GVO field rate (59.94 frames/sec NTSC, 50.00 frames/sec PAL) Page 1 GVO(7) GVO(7) |
|
hitachi(7) -- driver for Hitachi HDG-J series tablets
|
|
This driver is for the Hitachi HDG-J series of tablets. It will probably also work on other hitachi tablets capable of running in Hitachi III mode. It operates the tablets in high-resolution mode to provide for smooth drawing. These tablets provide x, y, height, pressure and tilt information. The driver uses hitachi as the X name of the device. (See input(7).) The difference between this drive and the driver called tablet, which is also for Hitachi tablets, is the use of high-resolution operatio... |
|
icmp(7) -- Internet Control Message Protocol
|
|
ICMP is the error and control message protocol used by IP and the Internet protocol family. It may be accessed through a "raw socket" for network monitoring and diagnostic functions. The proto parameter to the socket call to create an ICMP socket is obtained from getprotobyname(3N). ICMP sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) call may also be used to fix the destination for future packets (in which case the read(2) or recv(2)... |
|
ik(7) -- Ikon 10088 (ikc) parallel interface controller
|
|
This is the driver for the Ikon 10088 (and 10088A) parallel interface controller. The controller can support any one of three possible interfaces: Versatec TTL, Versatec differential, or (Tektronixcompatible) Centronics. The Ikon controller board must be jumpered, switched, connected, and terminated differently depending on which interface is being used. If the board is configured for the Centronics interface, bytes written to /dev/cent are output to the parallel port. A printer reset (input pri... |
|
imon(7) -- inode monitor device
|
|
The inode monitor driver is a pseudo device driver which enables a user level program to monitor filesystem activity on a file by file basis. The application program expresses interest in specific files by means of an ioctl request that specifies the pathname of the file and an indication of what types of events are to be monitored. As various actions take place on a file in which interest has been expressed, imon posts events through a queue that may be read via the read system call.... |
|
imp(7) -- driver for IMP wireless presentation mouse
|
|
IMPr is a wireless hand-held multimedia computer control device for use when giving presentations. IMP consists of a compact, battery-powered remote infra-red transmitter and a receiver that connects to the computer's serial port. With its unique force-sensitive Control Disc, IMP provides all the functions of a traditional mouse or trackball. IMP has a Manufacturer's Suggested Retail Price of $199. For sales or additional information, contact: Jack Copper ArcanaTech 120 South Whitfield Street ... |
|
inet(7) -- Internet protocol family
|
|
The Internet protocol family is a collection of protocols layered atop the Internet Protocol (IP) transport layer, and utilizing the Internet address format. The Internet family provides protocol support for the SOCK_STREAM, SOCK_DGRAM, and SOCK_RAW socket types; the SOCK_RAW interface provides access to the IP protocol. |
|
input(7) -- input devices
|
|
The calcomp tablet uses a streams module named "calcomp" but reports an X name of "tablet". The Drawing Pad II is 7" by 7" and has a resolution of 1000 points per inch. To scale raw tablet events to screen coordinates (1280x1024) we create /usr/lib/X11/input/config/tablet (name of X device) with the contents: x_init { scalewhich "none" scalex "914/5000" scaley "914/5000" scale0 "914/5000" scale1 "914/5000" } To make the calcomp tablet control the cursor automatically, we would ad... |
|
intro(7) -- introduction to special files
|
|
MAKEDEV(1M), fx(1M), hinv(1M), mt(1), prtvtoc(1M). |
|
ip(7) -- Internet Protocol
|
|
IP is the network layer protocol used by the Internet protocol family. Options may be set at the IP level when using higher-level protocols that are based on IP (such as TCP and UDP). It may also be accessed through a "raw socket" when developing new protocols, or special purpose applications. There are several IP-level setsockopt(2)/getsockopt(2) options. IP_OPTIONS may be used to provide IP header options to be transmitted in each outgoing packet or to examine the header options on incoming ... |
|
ipx(7) -- IPX Streams Multiplexor Driver
|
|
dlpi(7), ipxlink(1), ml(1M), snetd(1M) |
|
isdn(7) -- Integrated Services Digital Network
|
|
isdnd(1m), isdnstat(1m), ISDN User's Guide PPPPaaaaggggeeee 1111 |
|
jag(7) -- obsolete VME-SCSI disk driver
|
|
dksc(7M). PPPPaaaaggggeeee 1111 |
|
kbd(7) -- generalized string translation module
|
|
/usr/lib/kbd - directory containing system standard table files. /usr/lib/kbd/*.map - source for some system table files. |
|
keyboard(7) -- keyboard specifications
|
|
Indy, Indigo2, O2, OCTANE and Onyx2 use a PS/2 style keyboard (detailed in pckeyboard(7)) that uses a different scan code set. This difference may break compatibility for some programs that operate with raw scan codes. |
|
klog(7) -- kernel error logging interface
|
|
/dev/klog special file |
|
ldap(7) -- Lightweight Directory Access Protocol (Client)
|
|
Lightweight Directory Access Protocol (LDAP) is a specification for a client-server protocol to retrieve and manage directory information. Originally intended as a means for clients on lightweight workstations to access X.500 directories, it can be used with any directory system which follows the X.500 data model. The libns_ldap.so shared library contains routines to contact a remote LDAP server daemon, fetch information, and format it so that it is available to local name service routines. This... |
|
llc2(7) -- DLPI multiplexor-driver
|
|
dlpi(7) PPPPaaaaggggeeee 1111 |
|
log(7) -- interface to STREAMS error logging and event tracing
|
|
Example of I_ERRLOG notification. struct strioctl ioc; ioc.ic_cmd = I_ERRLOG; ioc.ic_timout = 0; /* default timeout (15 secs.) */ ioc.ic_len = 0; ioc.ic_dp = NULL; ... |
|
mdbm(7) -- local name service database
|
|
The mdbm client library fetches name service data out of an mdbm(3B) format database file on the local host. This library is meant to be used only by the nsd(1M) daemon to efficiently access local name service data. The library /var/ns/lib/libns_mdbm.so is opened by the nsd(1M) daemon when mdbm is listed as the protocol for some map in a nsswitch.conf file. The library contains code to fetch data from a local mdbm file and present it as lines from the configuration file from which it came. The n... |
|
mem(7) -- core memory
|
|
/dev/mem /dev/kmem /dev/mmem |
|
mouse(7) -- mouse specifications
|
|
Indy, Indigo2, O2, OCTANE and Onyx2 use a PS/2 style mouse, which is described in pcmouse(7). |
|
mtio(7) -- magnetic tape interface
|
|
Different drivers and drives support different tape commands, in the form of ioctl's. These operations and their structures are defined in the file /usr/include/sys/mtio.h, which has fairly extensive comments. All drivers support some common definitions of tape status via the MTIOCGET ioctl; in particular, the bits defined for the mt_dposn field of the mtget structure are the same for all the IRIX devices. other fields are driver specific, and the appropriate header files should be consulted fo... |
|
ndbm(7) -- local name service database
|
|
The ndbm client library fetches name service data out of an ndbm(3B) format database file on the local host. This library is meant to be used only by the nsd(1M) daemon to efficiently access local name service data. The library /var/ns/lib/libns_ndbm.so is opened by the nsd(1M) daemon when ndbm is listed as the protocol for some map in a nsswitch.conf file. The library contains code to fetch data from a local ndbm file and present it as lines from the configuration file from which it came. The n... |
|
netintro(7) -- introduction to networking facilities
|
|
This section briefly describes the networking facilities available in the system. Documentation in this part of section 7 is broken up into three areas: protocol families (domains), protocols, and network interfaces. Entries describing a protocol family are marked ``7F,'' while entries describing protocol use are marked ``7P.'' Hardware support for network interfaces are found among the standard ``7'' entries. All network protocols are associated with a specific protocol family. A protocol... |
|
nis(7) -- Network Information Services Protocol (Client)
|
|
The Network Information Services Protocol (NIS) is a simple Sun RPC based protocol to fetch keyed data from a remote host. It is typically used to distribute name service information in medium sized organizations. The data is maintained on a single host (designated the NIS master), and is pushed occasionally to a list of slave servers. Client systems dynamically locate a server and request data given a domain name, map name and key. In Irix the daemon nsd(1M) acts as both the server and client s... |
|
nisserv(7) -- Network Information Services Protocol (Server)
|
|
The Network Information Services Protocol (NIS) is a simple Sun RPC based protocol to fetch keyed data from a remote host. It is typically used to distribute name service information in medium sized organizations. The data is maintained on a single host (designated the NIS master), and is pushed occasionally to a list of slave servers. Client systems dynamically locate a server and request data given a domain name, map name and key. In Irix the daemon nsd(1M) acts as both the server and client s... |
|
null(7) -- the null file
|
|
/dev/null PPPPaaaaggggeeee 1111 |
|
nwfs(7) -- NetWare File System
|
|
ipx(7M) nwmount(1), ml(1M) PPPPaaaaggggeeee 2222 |
|
O2Video(7) -- O2 Video System
|
|
The vlGetFrontierMSC(3dm) manpage has the following statement under the CAVEATS section: For some VL devices, there is a short initial period (up to ten field times) in the lifetime of a transfer during which no frontier MSC is available. This period begins when the application calls Page 13 O2Video(7) O2Video(7) vlBeginTransfer(3dm) and ends when the device clocks in or out its first media stream sample from the application's VLBuffer. An attempt to call vlGetFrontierMSC(3dm) during this perio... |
|
par(7) -- process activity reporting device
|
|
/dev/par |
|
pciba(7) -- User level PCI Bus Adapter interface.
|
|
If the system does not support ULI, the /hw/.../pci/slot/intr vertex will not be present. If a boot prom allocates PCI space and sets up a device's BASE registers, and the values are not page aligned, pciba is unable to provide direct mmap service for those windows, and the corresponding /hw/.../pci/slot/base/bar, /hw/.../pci/slot/mem and /hw/.../pc<... |
|
pckeyboard(7) -- keyboard specifications
|
|
Some Silicon Graphics systems use a serial keyboard interface (detailed in keyboard(7)) that uses a different scan code set. This difference may break compatibility for some programs that operate with raw scan codes. |
|
pcmouse(7) -- mouse specifications
|
|
All Silicon Graphics systems, except those noted above use the mouse described in mouse(7). Some Silicon Graphics mice (particularly Silicon Graphics PN 9150800) look very similar to the old style Indigo2 mouse (Silicon Graphics PN 9150809) and even use the same 6-pin mini-DIN connector, but are not compatible. |
|
plp(7) -- parallel line printer interface
|
|
The special file /dev/plp refers to the parallel printer interface on the Indigo, Indy, Indigo2, Challenge/Onyx, O2, OCTANE, Origin200 and Onyx2 products. Special file /dev/plpbi is also available on the Indigo, Indy and Indigo2 platforms and is used to access the parallel printer interface in bidirectional access mode. The plp device supports output to a Centronics-compatible printer connected to the builtin parallel printer port. Normally, /dev/plp is directly accessed only by a print spooling... |
|
prf(7) -- operating system profiler
|
|
/dev/prf |
|
pty(7) -- pseudo terminal driver
|
|
The code sequence shown below demonstrates how to allocate pseudo terminals. Pseudo terminals, like all files, must have the correct file permissions to be accessible. The _getpty(3) library function takes care of this problem. #include #include /* * Find a pseudo tty to use and open both sides. * filedes[0] receives the master file descriptor while filedes[1] * receives the slave. The master is opened with O_NDELAY as commonly * needed in daemons such as rlogind and telnetd... |
|
raw(7) -- raw network protocol family
|
|
The Raw protocol family is a collection of input decapsulation protocols layered atop the data link protocol of a network interface. The Raw family supports only the SOCK_RAW socket type. |
|
root(7) -- partition names
|
|
/dev/dsk/dks* /dev/rdsk/dks* /dev/root /dev/usr /dev/swap /dev/rvh |
|
route(7) -- kernel packet forwarding database
|
|
The system provides some packet routing facilities. The kernel maintains a routing information database, which is used in selecting the appropriate network interface when transmitting packets. A user process (or possibly multiple co-operating processes) maintains this database by sending messages over a special kind of socket. This supplants fixed size ioctl(2)'s used in earlier releases. Routing table changes may only be carried out by the super user. The operating system may spontaneously emi... |
|
sad(7) -- STREAMS Administrative Driver
|
|
The STREAMS Administrative Driver provides an interface for applications to perform administrative operations on STREAMS modules and drivers. The interface is provided through ioctl(2) commands. Privileged operations may access the sad driver via /dev/sad/admin. Unprivileged operations may access the sad driver via /dev/sad/user. fildes is an open file descriptor that refers to the <... |
|
samba.7(7) -- A Windows SMB/CIFS fileserver for UNIX
|
|
The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems. This protocol is sometimes also referred to as the Common Internet File System (CIFS), LanManager or NetBIOS protocol. smbd The smbd daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager. The configuration file for this daemon is described in smb.conf nmbd The nmbd daemo... |
|
samp(7) -- Security Attribute Modulation Protocol
|
|
iflabel(1m), rhost(1m), satmpd(1m), trusted_networking(7), satmp(7p), tsix(7p) PPPPaaaaggggeeee 1111 |
|
satmp(7) -- Security Attribute Token Mapping Protocol (SATMP)
|
|
iflabel(1m), rhost(1m), satmpd(1m), trusted_networking(7), samp(7p), tsix(7p) PPPPaaaaggggeeee 1111 |
|
scsiha(7) -- SCSI bus and loop operation driver
|
|
The scsiha driver is used to pass requests to the scsi host adapter drivers to perform activities that aren't related to SCSI commands issued to individual devices. On parallel SCSI, this includes operations like resetting a SCSI bus and probing for devices. With Fibrechannel, it adds loop initialization, device reset and port bypass. All communication through the scsiha driver is via ioctls. Opens and closes automatically succeed. The ioctl structure is defined in , and is called s... |
|
serial(7) -- serial communication ports
|
|
All Silicon Graphics systems have two or more general purpose serial ports. These ports can be used to connect terminals, printers, modems, other systems, or graphical input devices such as a tablet or dial and button box. Each line can be independently set to run at any of several speeds. Various character echoing and interpreting parameters can also be set. See stty(1) and termio(7) for details on the various modes. Details of the serial ports found on optional add-on boards are given elsewher... |
|
smfd(7) -- driver for SCSI floppy and floptical disk drives
|
|
This driver supports 5 1/4" floppy drives in 3 standard formats when used with the freestanding SCSI floppy drive. The standard single and double density dual sided 3 1/2" drive and the 3 1/2" 20.1MB floptical drive is also supported. The driver also supports a large range of special formats by use of the SMFDSETMODE ioctl (defined along with the associated structure in /usr/include/sys/smfd.h). Most of the ioctls for the dksc also apply to this driver, with the exception of the bad block han... |
|
snoop(7) -- network monitoring protocol
|
|
The Snoop protocol provides promiscuous packet capture with filtering. It treats packets as datagrams containing a link-layer header followed by data. Snoop uses the Raw address format, assigning a unique port to a socket bound to port zero, otherwise binding the specified port if it is valid. Valid ports range from SNOOP_MINPORT to SNOOP_MAXPORT. Snoop associates a set of SNOOP_MAXFILTERS packet filters with each network interface. Each filter contains an array of mask bits, a parallel array of... |
|
stereo(7) -- stereo viewing on Silicon Graphics systems
|
|
There are four different types of stereo ports found on various Silicon Graphics systems. The DIN-8 powered serial port connectors, which are found on the Onyx and Crimson models, provide Stereo Sync in addition to serial communication signals for other types of peripherals. The serial signals are not used by external stereo viewing equipment, but the pin-out description of all signals on the DIN-8 is provided here for completeness. In order to support peripherals which draw power from the host ... |
|
stp(7) -- Scheduled Transfer Protocol
|
|
STP is a data transfer protocol that uses small control messages to prearrange data movement. Buffers are allocated at the sending and the receiving end before the data transmission, allowing full-rate, noncongesting data flow between the end devices. The control and data may use different physical media, or may share a single physical medium. The rea system calls should be used to transfer data over STP sockets. By the very nature of STP, a send operation on an STP socket must have a correspond... |
|
streamio(7) -- STREAMS ioctl commands
|
|
STREAMS [see intro(2)] ioctl commands are a subset of ioctl(2) system calls which perform a variety of control functions on streams. The arguments command and arg are passed to the file designated by fildes and are interpreted by the stream head. Certain combinations of these arguments may be passed to a module or driver in the stream. 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 i... |
|
sysctlr(7) -- Onyx and Challenge L/XL system controller communication device
|
|
The system controller device is used by sysctlrd to communicate with the Onyx and Challenge L/XL system controller. The system controller sequences power, monitors sensors, and drives the LCD front panel. Through this driver, sysctlrd(1M) reads sensor information, displays front panel messages, retrieves log messages, drives the CPU performance meter, and handles alarms. |
|
t3270(7) -- Silicon Graphics 3270 interface card
|
|
/dev/t3270 |
|
tcp(7) -- Internet Transmission Control Protocol
|
|
The TCP protocol provides reliable, flow-controlled, two-way transmission of data. It is a byte-stream protocol used to support the SOCK_STREAM abstraction. TCP uses the standard Internet address format and, in addition, provides a per-host collection of "port addresses". Thus, each address is composed of an Internet address specifying the host and network, with a specific TCP port on the host identifying the peer entity. Sockets utilizing the tcp protocol are either "active" or "passive".... |
|
termio(7) -- general terminal interfaces
|
|
All of the asynchronous communications ports use the same general interface, no matter what hardware is involved. The user interface to this functionality is via the ioctl calls described below, or the POSIX termios interface described in termios(3t). The remainder of this section discusses the common features of the terminal subsystem which are relevant to both of these interfaces. |
|
ticlts(7) -- loopback transport providers
|
|
The devices known as ticlts, ticots, and ticotsord are ``loopback transport providers,'' that is, stand-alone networks at the transport level. Loopback transport providers are transport providers in every sense except one: only one host (the local machine) is ``connected to'' a loopback network. Loopback transports present a TPI (STREAMS-level) interface to application processes and are intended to be accesse... |
|
timod(7) -- Transport Interface cooperating STREAMS module
|
|
<sys/timod.h> <sys/tiuser.h> <sys/tihdr.h> <sys/errno.h> |
|
tirdwr(7) -- Transport Interface read/write interface STREAMS module
|
|
streamio(7), timod(7) intro(2), getmsg(2), putmsg(2), read(2), write(2), intro(3) PPPPaaaaggggeeee 2222 |
|
tokenring(7) -- IRIS-4D Series Token Ring controllers
|
|
Various error messages are printed by the kernel when a problem is encountered. The message is preceded by the controller name, for example, mtr0. If they occur repeatedly, contact your product support service for assistance. Use the mtrconfig(1M) command to determine the software revision number. Counts of Token Ring input and output errors can be displayed with the command netstat -i (see netstat(1M)).... |
|
tps(7) -- SCSI tape interface
|
|
Silicon Graphics systems support the Small Computer System Interface (SCSI) for various tape drives, including QIC24 and QIC150 1/4" cartridges, 9-track, 8 mm video, Ampex DIS/DST series, DLT (digital linear tape), IBM 3590 and 3570, STK 9490 and 9840, STK SD3, Sony GY-10 and GY-2120, and DAT (digital audio tape) tape drives. Not all systems support all tape drives. Since so many different types of devices are supported, and not all their features can be determined directly from the drive, a co... |
|
trusted_networking(7) -- Trusted IRIX network administration: basic concepts.
|
|
In the current release of Trusted IRIX, the policies enforced by the trusted networking code are as follows. Transmitted packet labels must fall within the label range of the destination host or network profile in the remote host database. Received packet labels must fall within the label range of the source host or network profile in the remote host database. Delivered data must have a label equal to the label of the receiving process. The uid of the delivered data must be permitted by the sock... |
|
ts(7) -- tape support
|
|
The tape support (TS) system consists of a tape support driver, personality daemons, and a daemon to manage the personality daemons. For information on how to configure tape support, see the ts.config(4) man page. The tape support driver passes all device-dependent tasks, except for I/O processing, to a personality daemon. For optimal performance, I/O requests are processed in the driver. There is a personality daemon for each device type supported by the tape support ... |
|
tsd(7) -- TELNET server protocol STREAMS device
|
|
/dev/tnclone - telnet stream clone device /dev/tty[ghij][0-0xff] - telnet streams terminals |
|
tsix(7) -- Trusted Security Information Exchange
|
|
libt6(3N), iflabel(1m), rhost(1m), trusted_networking(7), satmpd(1m), satmp(7p), samp(7p) PPPPaaaaggggeeee 1111 |
|
tty(7) -- controlling terminal interface
|
|
/dev/tty /dev/tty* |
|
udp(7) -- Internet User Datagram Protocol
|
|
UDP is a simple, unreliable datagram protocol which is used to support the SOCK_DGRAM abstraction for the Internet protocol family. UDP sockets are connectionless, and are normally used with the sendto and recvfrom calls, though the connect(2) call may also be used to fix the destination for future packets (in which case the recv(2) or rea or write(2) system calls may be used). UDP address formats are identical to those used by TCP. In particular UDP provides a port identifier in addition to the... |
|
unix(7) -- UNIX-domain protocol family
|
|
The UNIX-domain protocol family is a collection of protocols that provides local (on-machine) interprocess communication through the normal socket(2) mechanisms. The UNIX-domain family supports the SOCK_STREAM and SOCK_DGRAM socket types and uses filesystem pathnames for addressing. |
|
usb(7) -- Irix USB subsystem
|
|
The SGI USB implemtation is a partial implementation, intended to provide support for selected keyboards and mice (see usbinput(7)) for Onyx3. Currently there is no administrative command for individual device control, and there is no support for devices other than keyboard/mouse. Likewise, the usb infrastructure provides no published api for the implentation of new usb drivers. Only controllers conforming to the OpenHCI spec are supported.... |
|
usbinput(7) -- Onyx3 usb keyboard and mouse input
|
|
In order to minimize changes to application code, the usb keyboard and mouse driver convert usb usage codes to ps2 scan code sequences at the /dev/input[N]/keyboard devices. Likewise ps2 mouse codes are generated at /dev/input[N]/mouse. The entry points /dev/input/keyboard and /dev/input/mouse will always exist. If there is no corresponding physical device (ie. no keyboard and/or mouse with device id 0), the device will operate similar to /dev/null. If an application has the device open in this ... |
|
usema(7) -- software semaphore driver
|
|
The usema driver is intended to be used only by the standard library spinlock and semaphore routines. Client programs should use these routines, rather than using usema directly. |
|
usrdma(7) -- User-Level DMA engine support interface.
|
|
The special files associated with the user-level DMA engine support interface provide access to DMA engines via the library udmalib(3X). These files should not be accessed directly by a user. Currently, the only DMA engine supported is under VME on the Challenge/Onyx series. However, as more DMA engines become available for VME and other busses on other platforms, access will be provided through this interface.... |
|
usrpci(7) -- Obsolete User level PCI Bus adapter interface.
|
|
pciba PPPPaaaaggggeeee 1111 |
|
usrvme(7) -- User level VME Bus adapter interface.
|
|
"IRIX Device Driver Programmer's Guide" hinv(1M) MAKEDEV(1M) -- on Challenge and Onyx systems. PPPPaaaaggggeeee 2222 |
|
vh(7) -- disk volume header
|
|
/dev/rvh /dev/rdsk/*vh |
|
vino(7) -- on-board video input system for Indy
|
|
VINO supports frame(field) capture that is decimated in both the X and Y directions. Decimation of sizes 1/2th, 1/3rd, 1/4th, 1/5th, 1/6th, 1/7th and 1/8th are supported, though the color quality suffers at the smaller ranges. To compensate for this limitation, the system software initiates a decimation conversion for values 1/4th, 1/6th and 1/8th by doing the first half of the decimation in hardware and the second half of the decimation in software. This affects the software overhead required f... |
|
xlv(7) -- logical volume disk driver
|
|
XLV devices provide access to disk storage as logical volumes. A logical volume is an object that behaves like a disk partition, but its storage can span several physical disk devices. Using XLV, you can concatenate disks together to create larger logical volumes, stripe data across disks to create logical volumes with greater throughput, and plex (or mirror) disks for reliability. In addition, XLV enables you to change the configuration of volumes while the volume is actively being used as a fi... |
|
zero(7) -- source of zeroes
|
|
/dev/zero |
