1 '\" te 2 .\" Copyright (c) 1999, Sun Microsystems, Inc. All Rights Reserved. 3 .\" Copyright 1989 AT&T 4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. 5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. 6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] 7 .TH INTRO 7 "Sep 29, 1994" 8 .SH NAME 9 Intro, intro \- introduction to special files 10 .SH DESCRIPTION 11 .sp 12 .LP 13 This section describes various device and network interfaces available on the 14 system. The types of interfaces described include character and block 15 devices, STREAMS modules, network protocols, file systems, and ioctl requests 16 for driver subsystems and classes. 17 .sp 18 .LP 19 This section contains the following major collections: 20 .sp 21 .ne 2 22 .na 23 \fB(7D)\fR 24 .ad 25 .RS 9n 26 The system provides drivers for a variety of hardware devices, such as disk, 27 magnetic tapes, serial communication lines, mice, and frame buffers, as well 28 as virtual devices such as pseudo-terminals and windows. 29 .sp 30 This section describes special files that refer to specific hardware 31 peripherals and device drivers. STREAMS device drivers are also described. 32 Characteristics of both the hardware device and the corresponding device driver 33 are discussed where applicable. 34 .sp 35 An application accesses a device through that device's special file. This 36 section specifies the device special file to be used to access the device as 37 well as application programming interface (API) information relevant to the use 38 of the device driver. 39 .sp 40 All device special files are located under the \fB/devices\fR directory. The 41 \fB/devices\fR directory hierarchy attempts to mirror the hierarchy of system 42 busses, controllers, and devices configured on the system. Logical device 43 names for special files in \fB/devices\fR are located under the \fB/dev\fR 44 directory. Although not every special file under \fB/devices\fR will have a 45 corresponding logical entry under \fB/dev\fR, whenever possible, an 46 application should reference a device using the logical name for the device. 47 Logical device names are listed in the \fBFILES\fR section of the page for the 48 device in question. 49 .sp 50 This section also describes driver configuration where applicable. Many device 51 drivers have a driver configuration file of the form 52 \fIdriver_name\fR\fB\&.conf\fR associated with them (see 53 \fBdriver.conf\fR(4)). The configuration information stored in the driver 54 configuration file is used to configure the driver and the device. Driver 55 configuration files are located in \fB/kernel/drv\fR and 56 \fB/usr/kernel/drv\fR. Driver configuration files for platform dependent 57 drivers are located in \fB/platform/`uname\fR \fB-i`/kernel/drv\fR where 58 \fB`uname\fR \fB-i`\fR is the output of the \fBuname\fR(1) command with the 59 \fB-i\fR option. 60 .sp 61 Some driver configuration files may contain user configurable properties. 62 Changes in a driver's configuration file will not take effect until the system 63 is rebooted or the driver has been removed and re-added (see \fBrem_drv\fR(1M) 64 and \fBadd_drv\fR(1M)). 65 .RE 66 67 .sp 68 .ne 2 69 .na 70 \fB(7FS)\fR 71 .ad 72 .RS 9n 73 This section describes the programmatic interface for several file systems 74 supported by SunOS. 75 .RE 76 77 .sp 78 .ne 2 79 .na 80 \fB(7I)\fR 81 .ad 82 .RS 9n 83 This section describes ioctl requests which apply to a class of drivers or 84 subsystems. For example, ioctl requests which apply to most tape devices are 85 discussed in \fBmtio\fR(7I). Ioctl requests relevant to only a specific 86 device are described on the man page for that device. The page for the device 87 in question should still be examined for exceptions to the ioctls listed in 88 section 7I. 89 .RE 90 91 .sp 92 .ne 2 93 .na 94 \fB(7M)\fR 95 .ad 96 .RS 9n 97 This section describes \fBSTREAMS\fR modules. Note that \fBSTREAMS\fR 98 drivers are discussed in section 7D. \fBstreamio\fR(7I) contains a list of 99 ioctl requests used to manipulate \fBSTREAMS\fR modules and interface with the 100 \fBSTREAMS\fR framework. Ioctl requests specific to a \fBSTREAMS\fR module 101 will be discussed on the man page for that module. 102 .RE 103 104 .sp 105 .ne 2 106 .na 107 \fB(7P)\fR 108 .ad 109 .RS 9n 110 This section describes various network protocols available in SunOS. 111 .sp 112 SunOS supports both socket-based and \fBSTREAMS-based\fR network 113 communications. The Internet protocol family, described in \fBinet\fR(7P), is 114 the primary protocol family supported by SunOS, although the system can support 115 a number of others. The raw interface provides low-level services, such as 116 packet fragmentation and reassembly, routing, addressing, and basic transport 117 for socket-based implementations. Facilities for communicating using an 118 Internet-family protocol are generally accessed by specifying the \fBAF_INET\fR 119 address family when binding a socket; see \fBsocket\fR(3SOCKET) for details. 120 .sp 121 Major protocols in the Internet family include: 122 .RS +4 123 .TP 124 .ie t \(bu 125 .el o 126 The Internet Protocol (IP) itself, which supports the universal datagram 127 format, as described in \fBip\fR(7P). This is the default protocol for 128 \fBSOCK_RAW\fR type sockets within the \fBAF_INET\fR domain. 129 .RE 130 .RS +4 131 .TP 132 .ie t \(bu 133 .el o 134 The Transmission Control Protocol (TCP); see \fBtcp\fR(7P). This is the default 135 protocol for \fBSOCK_STREAM\fR type sockets. 136 .RE 137 .RS +4 138 .TP 139 .ie t \(bu 140 .el o 141 The User Datagram Protocol (UDP); see \fBudp\fR(7P). This is the default 142 protocol for \fBSOCK_DGRAM\fR type sockets. 143 .RE 144 .RS +4 145 .TP 146 .ie t \(bu 147 .el o 148 The Address Resolution Protocol (ARP); see \fBarp\fR(7P). 149 .RE 150 .RS +4 151 .TP 152 .ie t \(bu 153 .el o 154 The Internet Control Message Protocol (ICMP); see \fBicmp\fR(7P). 155 .RE 156 .RE 157 158 .SH SEE ALSO 159 .sp 160 .LP 161 \fBadd_drv\fR(1M), \fBrem_drv\fR(1M), \fBIntro\fR(3), \fBioctl\fR(2), 162 \fBsocket\fR(3SOCKET), \fBdriver.conf\fR(4), \fBarp\fR(7P), \fBicmp\fR(7P), 163 \fBinet\fR(7P), \fBip\fR(7P), \fBmtio\fR(7I), \fBst\fR(7D), \fBstreamio\fR(7I), 164 \fBtcp\fR(7P), \fBudp\fR(7P) 165 .sp 166 .LP 167 \fISystem Administration Guide: IP Services\fR 168 .sp 169 .LP 170 \fISTREAMS Programming Guide\fR 171 .sp 172 .LP 173 \fIWriting Device Drivers\fR