Lines Matching +full:sub +full:- +full:node
8 devlinks \- adds /dev entries for miscellaneous devices and pseudo-devices
12 \fB/usr/sbin/devlinks\fR [\fB-d\fR] [\fB-r\fR \fIrootdir\fR] [\fB-t\fR \fItable-file\fR]
23 actual block- and character-special device nodes under the \fB/devices\fR
25 \fItable-file\fR (by default \fB/etc/devlink.tab\fR).
28 \fBdevlinks\fR is called each time the system is reconfiguration-booted, and
32 The \fItable-file\fR (normally \fB/etc/devlink.tab\fR) is an ASCII file, with
43 \fB\fIdevfs-spec\fR\fR
47 specification consists of one or more keyword-value pairs, where the keyword is
48 separated from the value by an equal-sign (`\fB=\fR'), and keyword-value pairs
68 The name of the node. This is the portion of the \fB/devices\fR tree entry name
78 The address portion of a node name. This is the portion of a node name that
80 a node may have a name without an address part, which is the case for many of
81 the pseudo-device nodes. If a number is given after the \fIaddr\fR it specifies
82 a match of a particular comma-separated subfield of the address field:
93 The minor portion of a node name \(mi the portion of the name after the
111 escape-sequences to allow portions of the \fB/devices\fR name to be included in
112 the \fB/dev\fR name, \fIor\fR to allow a counter to be used in creating node
115 \fB/dev/\fR-subdirectory that match (up to and including the counter) are
118 \fB/devices/\fR-tree
120 The possible escape-sequences are:
127 Substitute the \fBdevice-name\fR (name) portion of the corresponding devinfo
128 node-name.
138 corresponding devinfo node name. Sub-components are separated by commas, and
139 sub-component \fB0\fR is the whole \fBaddress\fR component.
148 Substitute the \fIn\fRth sub-component of the \fBminor\fR component of the
149 corresponding devinfo node name. Sub-components are separated by commas, and
150 sub-component \fB0\fR is the whole \fBminor\fR component.
160 counter for each dev-spec, and counter-values will be selected so they are as
161 low as possible while not colliding with already-existing link names.
163 In a dev-spec the \fBcounter\fR sequence should not be followed by a digit,
164 either explicitly or as a result of another escape-sequence expansion. If this
165 occurs, it would not be possible to correctly match already-existing links to
167 the already-existing \fB/dev\fR-name.
175 \fB\fIextra-dev-link\fR\fR
180 escape-sequence (as described for the \fIdev-spec\fR field) but may not contain
181 any of the other escape-sequences. It provides a way to specify an alias of a
192 \fB\fB-d\fR\fR
202 \fB\fB-r\fR \fIrootdir\fR\fR
208 is the root directory applied to the filename supplied to the \fB-t\fR option.
214 \fB\fB-t\fR \fItable-file\fR\fR
220 piece of work, since just the links-types that \fBdevlinks\fR is supposed to
221 create can be specified in a command-file and fed to \fBdevlinks\fR.
227 If \fBdevlinks\fR finds an error in a line of the \fItable-file\fR it prints a
229 \fItable-file\fR without performing any of the actions specified by the
233 If it cannot create a link for some filesystem-related reason it prints an
234 error-message and continues with the current rule.
238 the next \fItable-file\fR line.
258 is the minor-component of the \fIdevinfo-name\fR (this is always a single-digit
294 the default rule-file
307 It is very easy to construct mutually-contradictory link specifications, or