|
|
|
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 |
