Print this page
12144 Convert Intro(7) to mandoc
12145 Convert cpr(7) to mandoc
12146 Convert ibmf(7) to mandoc
12147 Convert FSS(7) to mandoc
Reviewed by: Peter Tribble <peter.tribble@gmail.com>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man7/Intro.7.man.txt
+++ new/usr/src/man/man7/Intro.7.man.txt
1 1 INTRO(7) Device and Network Interfaces INTRO(7)
2 2
3 -
4 -
5 3 NAME
6 - Intro, intro - introduction to special files
4 + Intro, intro - introduction to special files
7 5
8 6 DESCRIPTION
9 - This section describes various device and network interfaces available
10 - on the system. The types of interfaces described include character
11 - and block devices, STREAMS modules, network protocols, file systems,
12 - and ioctl requests for driver subsystems and classes.
7 + This section describes various device and network interfaces available on
8 + the sysstem. The types of interfaces described include character and
9 + block devices, STREAMS modules, network protocols, file systems, and
10 + ioctl requests for driver subsystems and classes.
13 11
12 + This section contains the following major collections:
14 13
15 - This section contains the following major collections:
14 + (7D) The system provides drivers for a variety of hardware devices,
15 + such as disk, magnetic tapes, serial communication lines, mice,
16 + and frame buffers, as well as virtual devices such as pseudo-
17 + terminals and windows.
16 18
17 - (7D)
18 - The system provides drivers for a variety of hardware devices,
19 - such as disk, magnetic tapes, serial communication lines,
20 - mice, and frame buffers, as well as virtual devices such as
21 - pseudo-terminals and windows.
19 + This section describes special files that refer to specific
20 + hardware peripherals and device drivers. STREAMS device drivers
21 + are also described. Characteristics of both the hardware device
22 + and the corresponding device driver are discussed where
23 + applicable.
22 24
23 - This section describes special files that refer to specific
24 - hardware peripherals and device drivers. STREAMS device
25 - drivers are also described. Characteristics of both the
26 - hardware device and the corresponding device driver are
27 - discussed where applicable.
25 + An application accesses a device through that device's special
26 + file. This section specifies the device special file to be used
27 + to access the device as well as application programming interface
28 + (API) information relevant to the use of the device driver. All
29 + device special files are located under the /devices directory.
30 + The /devices directory hierarchy attempts to mirror the hierarchy
31 + of system busses, controllers, and devices configured on the
32 + system. Logical device names for special files in /devices are
33 + located under the /dev directory. Although not every special file
34 + under /devices will have a corresponding logical entry under /dev,
35 + whenever possible, an application should reference a device using
36 + the logical name for the device. Logical device names are listed
37 + in the FILES section of the page for the device in question.
28 38
29 - An application accesses a device through that device's special
30 - file. This section specifies the device special file to be
31 - used to access the device as well as application programming
32 - interface (API) information relevant to the use of the device
33 - driver.
39 + This section also describes driver configuration where applicable.
40 + Many device drivers have a driver configuration file of the form
41 + driver_name.conf associated with them (see driver.conf(4)). The
42 + configuration information stored in the driver configuration file
43 + is used to configure the driver and the device. Driver
44 + configuration files are located in /kernel/drv and
45 + /usr/kernel/drv. Driver configuration files for platform
46 + dependent drivers are located in /platform/`uname -i`/kernel/drv
47 + where `uname -i` is the output of the uname(1) command with the -i
48 + option.
34 49
35 - All device special files are located under the /devices
36 - directory. The /devices directory hierarchy attempts to
37 - mirror the hierarchy of system busses, controllers, and
38 - devices configured on the system. Logical device names for
39 - special files in /devices are located under the /dev
40 - directory. Although not every special file under /devices will
41 - have a corresponding logical entry under /dev, whenever
42 - possible, an application should reference a device using the
43 - logical name for the device. Logical device names are listed
44 - in the FILES section of the page for the device in question.
50 + Some driver configuration files may contain user configurable
51 + properties. Changes in a driver's configuration file will not
52 + take effect until the system is rebooted or the driver has been
53 + removed and re-added (see rem_drv(1M) and add_drv(1M)).
45 54
46 - This section also describes driver configuration where
47 - applicable. Many device drivers have a driver configuration
48 - file of the form driver_name.conf associated with them (see
49 - driver.conf(4)). The configuration information stored in the
50 - driver configuration file is used to configure the driver and
51 - the device. Driver configuration files are located in
52 - /kernel/drv and /usr/kernel/drv. Driver configuration files
53 - for platform dependent drivers are located in
54 - /platform/`uname -i`/kernel/drv where `uname -i` is the output
55 - of the uname(1) command with the -i option.
55 + (7FS) This section describes the programmatic interface for several file
56 + systems supported by SunOS.
56 57
57 - Some driver configuration files may contain user configurable
58 - properties. Changes in a driver's configuration file will not
59 - take effect until the system is rebooted or the driver has
60 - been removed and re-added (see rem_drv(1M) and add_drv(1M)).
58 + (7I) This section describes ioctl requests which apply to a class of
59 + drivers or subsystems. For example, ioctl requests which apply to
60 + most tape devices are discussed in mtio(7I). Ioctl requests
61 + relevant to only a specific device are described on the man page
62 + for that device. The page for the device in question should still
63 + be examined for exceptions to the ioctls listed in section 7I.
61 64
65 + (7M) This section describes STREAMS modules. Note that STREAMS drivers
66 + are discussed in section 7D. streamio(7I) contains a list of
67 + ioctl requests used to manipulate STREAMS modules and interface
68 + with the STREAMS framework. ioctl(2) requests specific to a
69 + STREAMS module will be discussed on the man page for that module.
62 70
63 - (7FS)
64 - This section describes the programmatic interface for several
65 - file systems supported by SunOS.
71 + (7P) This section describes various network protocols available in
72 + SunOS. SunOS supports both socket-based and STREAMS-based network
73 + communications.
66 74
75 + The Internet protocol family, described in inet(7P), is the
76 + primary protocol family supported by SunOS, although the system
77 + can support a number of others. The raw interface provides low-
78 + level services, such as packet fragmentation and reassembly,
79 + routing, addressing, and basic transport for socket-based
80 + implementations. Facilities for communicating using an Internet-
81 + family protocol are generally accessed by specifying the AF_INET
82 + address family when binding a socket; see socket(3SOCKET) for
83 + details.
67 84
68 - (7I)
69 - This section describes ioctl requests which apply to a class
70 - of drivers or subsystems. For example, ioctl requests which
71 - apply to most tape devices are discussed in mtio(7I). Ioctl
72 - requests relevant to only a specific device are described on
73 - the man page for that device. The page for the device in
74 - question should still be examined for exceptions to the ioctls
75 - listed in section 7I.
85 + Major protocols in the Internet family include:
76 86
87 + o The Internet Protocol (IP) itself, which supports the
88 + universal datagram format, as described in ip(7P). This
89 + is the default protocol for SOCK_RAW type sockets within
90 + the AF_INET domain.
77 91
78 - (7M)
79 - This section describes STREAMS modules. Note that STREAMS
80 - drivers are discussed in section 7D. streamio(7I) contains a
81 - list of ioctl requests used to manipulate STREAMS modules and
82 - interface with the STREAMS framework. Ioctl requests specific
83 - to a STREAMS module will be discussed on the man page for
84 - that module.
92 + o The Transmission Control Protocol (TCP); see tcp(7P).
93 + This is the default protocol for SOCK_STREAM type
94 + sockets.
85 95
96 + o The User Datagram Protocol (UDP); see udp(7P). This is
97 + the default protocol for SOCK_DGRAM type sockets.
86 98
87 - (7P)
88 - This section describes various network protocols available in
89 - SunOS.
99 + o The Address Resolution Protocol (ARP); see arp(7P).
90 100
91 - SunOS supports both socket-based and STREAMS-based network
92 - communications. The Internet protocol family, described in
93 - inet(7P), is the primary protocol family supported by SunOS,
94 - although the system can support a number of others. The raw
95 - interface provides low-level services, such as packet
96 - fragmentation and reassembly, routing, addressing, and basic
97 - transport for socket-based implementations. Facilities for
98 - communicating using an Internet-family protocol are generally
99 - accessed by specifying the AF_INET address family when binding
100 - a socket; see socket(3SOCKET) for details.
101 + o The Internet Control Message Protocol (ICMP); see
102 + icmp(7P).
101 103
102 - Major protocols in the Internet family include:
103 -
104 - o The Internet Protocol (IP) itself, which supports
105 - the universal datagram format, as described in
106 - ip(7P). This is the default protocol for SOCK_RAW
107 - type sockets within the AF_INET domain.
108 -
109 - o The Transmission Control Protocol (TCP); see
110 - tcp(7P). This is the default protocol for
111 - SOCK_STREAM type sockets.
112 -
113 - o The User Datagram Protocol (UDP); see udp(7P). This
114 - is the default protocol for SOCK_DGRAM type
115 - sockets.
116 -
117 - o The Address Resolution Protocol (ARP); see arp(7P).
118 -
119 - o The Internet Control Message Protocol (ICMP); see
120 - icmp(7P).
121 -
122 -
123 104 SEE ALSO
124 - add_drv(1M), rem_drv(1M), Intro(3), ioctl(2), socket(3SOCKET),
125 - driver.conf(4), arp(7P), icmp(7P), inet(7P), ip(7P), mtio(7I), st(7D),
126 - streamio(7I), tcp(7P), udp(7P)
105 + add_drv(1M), rem_drv(1M), ioctl(2), Intro(3), socket(3SOCKET),
106 + driver.conf(4), st(7D), mtio(7I), streamio(7I), arp(7P), icmp(7P),
107 + inet(7P), ip(7P), tcp(7P), udp(7P)
127 108
109 + System Administration Guide: IP Services
128 110
129 - System Administration Guide: IP Services
111 + STREAMS Programming Guide
130 112
113 + Writing Device Drivers
131 114
132 - STREAMS Programming Guide
133 -
134 -
135 - Writing Device Drivers
136 -
137 -
138 -
139 - September 29, 1994 INTRO(7)
115 +illumos January 6, 2020 illumos
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX