1devfsadm(1M) System Administration Commands devfsadm(1M)
2
3
4
6 devfsadm, devfsadmd - administration command for /dev
7
9 /usr/sbin/devfsadm [-C] [-c device_class] [-i driver_name]
10 [ -n] [-r root_dir] [-s] [-t table_file] [-v]
11
12
13 /usr/lib/devfsadm/devfsadmd
14
15
17 devfsadm(1M) maintains the /dev namespace. It replaces the previous
18 suite of devfs administration tools including drvconfig(1M), disks(1M),
19 tapes(1M), ports(1M), audlinks(1M), and devlinks(1M).
20
21
22 The default operation is to attempt to load every driver in the system
23 and attach to all possible device instances. Next, devfsadm creates
24 logical links to device nodes in /dev and /devices and loads the device
25 policy.
26
27
28 devfsadmd(1M) is the daemon version of devfsadm(1M). The daemon is
29 started during system startup and is responsible for handling both
30 reconfiguration boot processing and updating /dev and /devices in
31 response to dynamic reconfiguration event notifications from the ker‐
32 nel.
33
34
35 For compatibility purposes, drvconfig(1M), disks(1M), tapes(1M),
36 ports(1M), audlinks(1M), and devlinks(1M) are implemented as links to
37 devfsadm.
38
39
40 In addition to managing /dev, devfsadm also maintains the
41 path_to_inst(4) database.
42
44 The following options are supported:
45
46 -C Cleanup mode. Prompt devfsadm to cleanup dangling
47 /dev links that are not normally removed. If the -c
48 option is also used, devfsadm only cleans up for the
49 listed devices' classes.
50
51
52 -c device_class Restrict operations to devices of class
53 device_class. Solaris defines the following values
54 for device_class: disk, tape, port, audio, and
55 pseudo. This option might be specified more than
56 once to specify multiple device classes.
57
58
59 -i driver_name Configure only the devices for the named driver,
60 driver_name.
61
62
63 -n Do not attempt to load drivers or add new nodes to
64 the kernel device tree.
65
66
67 -s Suppress any changes to /dev. This is useful with
68 the -v option for debugging.
69
70
71 -t table_file Read an alternate devlink.tab file. devfsadm nor‐
72 mally reads /etc/devlink.tab.
73
74
75 -r root_dir Presume that the /dev directory trees are found
76 under root_dir, not directly under root (/). No
77 other use or assumptions are made about root_dir.
78
79
80 -v Print changes to /dev in verbose mode.
81
82
84 The following exit values are returned:
85
86 0 Successful completion.
87
88
89 1 An error occurred.
90
91
93 /devices
94
95 device nodes directory
96
97
98 /dev
99
100 logical symbolic links to /devices
101
102
103 /usr/lib/devfsadm/devfsadmd
104
105 devfsadm daemon
106
107
108 /dev/.devfsadm_dev.lock
109
110 update lock file
111
112
113 /dev/.devfsadm_daemon.lock
114
115 daemon lock file
116
117
118 /etc/security/device_policy
119
120 device policy file
121
122
123 /etc/security/extra_privs
124
125 additional device privileges
126
127
129 See attributes(5) for descriptions of the following attributes:
130
131
132
133
134 ┌─────────────────────────────┬─────────────────────────────┐
135 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
136 ├─────────────────────────────┼─────────────────────────────┤
137 │Availability │SUNWcsu │
138 └─────────────────────────────┴─────────────────────────────┘
139
141 svcs(1), add_drv(1M), modinfo(1M), modload(1M), modunload(1M),
142 rem_drv(1M), svcadm(1M), tapes(1M), path_to_inst(4), attributes(5),
143 privileges(5), smf(5), devfs(7FS)
144
146 This document does not constitute an API. The /devices directory might
147 not exist or might have different contents or interpretations in a
148 future release. The existence of this notice does not imply that any
149 other documentation that lacks this notice constitutes an API.
150
151
152 devfsadm no longer manages the /devices name space. See devfs(7FS).
153
154
155 The device configuration service is managed by the service management
156 facility, smf(5), under the service identifier, and can be used to
157 start devfsadm during reconfiguration boot by:
158
159 svc:/system/device/local:default
160
161
162
163
164 Otherwise, devfsadm is started by:
165
166 svc:/system/sysevent:default
167
168
169
170
171 Administrative actions on this service, such as enabling, disabling, or
172 requesting restart, can be performed using svcadm(1M). The service's
173 status can be queried using the svcs(1) command.
174
175
176
177SunOS 5.11 23 Jun 2008 devfsadm(1M)