AuxXxilium/eudev
1
0
Fork 0
mirror of https://github.com/AuxXxilium/eudev.git synced 2024-11-23 23:10:57 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity

Improve wording and restore lines lost in merges

Browse Source 
Generate udev.7 from udev.xml
This commit is contained in:
Boian Bonev 2023-09-30 22:29:22 +00:00
parent 805c07a07b
commit 218489052f
No known key found for this signature in database
GPG Key ID: 1365720913D2F22D
2 changed files with 38 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
man/udev.7
View File

@ -23,9 +23,9 @@
udev \- Dynamic device management
.SH "DESCRIPTION"
.PP
udev supplies the system software with device events, manages permissions of device nodes and may create additional symlinks in the
udev supplies the system software with device events, manages permissions of device nodes, may create additional symlinks in the
/dev
directory, or renames network interfaces\&. The kernel usually just assigns unpredictable device names based on the order of discovery\&. Meaningful symlinks or network device names provide a way to reliably identify devices based on their properties or current configuration\&.
directory and may rename network interfaces\&. The kernel usually just assigns unpredictable device names based on the order of discovery\&. Meaningful symlinks or network device names provide a way to reliably identify devices based on their properties or current configuration\&.
.PP
The udev daemon,
\fBudevd\fR(8), receives device uevents directly from the kernel whenever a device is added or removed from the system, or it changes its state\&. When udev receives a device event, it matches its configured set of rules against various device attributes to identify the device\&. Rules that match may provide additional device information to be stored in the udev database or to be used to create meaningful symlink names\&.
@ -539,18 +539,17 @@ character itself\&.
.PP
The hwdb files are read from the files located in the system hwdb directory
/usr/lib/udev/hwdb\&.d, the volatile runtime directory
/run/udev/hwdb\&.d
the local administration directory
/run/udev/hwdb\&.d, the local administration directory
/etc/udev/hwdb\&.d, and any other directory in the
\fBUDEV_HWDB_PATH\fR
search path variable\&. All hwdb files are collectively sorted and processed in lexical order, regardless of the directories in which they live\&. However, files with identical filenames replace each other\&. Files in
/etc
have the highest priority, files in
/run
take precedence over files with the same name in
/usr/lib, and the content of
have the highest priority, then files in
/run,
/usr/lib
and the ones in
\fBUDEV_HWDB_PATH\fR
comes last\&. This order can be used to override a system\-supplied hwdb file with a local file if needed; a symlink in
comes last\&. Files with higher priority take precedence over files with the same name and lower priority\&. This order can be used to override a system\-supplied hwdb file with a local file if needed; a symlink in
/etc
with the same name as a hwdb file in
/usr/lib, pointing to
@ -568,11 +567,9 @@ The content of all hwdb files is read by
\fBudevadm\fR(8)
and compiled to a binary database located at
/etc/udev/hwdb\&.bin, or alternatively
/usr/lib/udev/hwdb\&.bin
if you want ship the compiled database in an immutable image by using
/usr/lib/udev/hwdb\&.bin, if you want to ship the compiled database in an immutable image by using
\fB\-\-usr\fR, or anywhere on the system by using
\fB\-\-output\fR\&. During runtime only the binary database is used\&.
If
\fB\-\-output\fR\&. If
\fBUDEV_HWDB_BIN\fR
is set at run\-time, and its value identifies a file in the file system, then the binary database located under this name will be used\&. During runtime only the binary database is used\&.
.SH "SEE ALSO"

52
man/udev.xml
View File

@ -35,8 +35,8 @@
<refsect1><title>Description</title>
<para>udev supplies the system software with device events, manages permissions
of device nodes and may create additional symlinks in the <filename>/dev</filename>
directory, or renames network interfaces. The kernel usually just assigns unpredictable
of device nodes, may create additional symlinks in the <filename>/dev</filename>
directory and may rename network interfaces. The kernel usually just assigns unpredictable
device names based on the order of discovery. Meaningful symlinks or network device
names provide a way to reliably identify devices based on their properties or
current configuration.</para>
@ -737,21 +737,22 @@
<refsect1><title>Hardware Database Files</title>
<para>The hwdb files are read from the files located in the
system hwdb directory <filename>/usr/lib/udev/hwdb.d</filename>,
the volatile runtime directory <filename>/run/udev/hwdb.d</filename>
the volatile runtime directory <filename>/run/udev/hwdb.d</filename>,
the local administration directory <filename>/etc/udev/hwdb.d</filename>,
and any other directory in the <envar>UDEV_HWDB_PATH</envar> search path variable.
All hwdb files are collectively sorted and processed in lexical order,
regardless of the directories in which they live. However, files with
identical filenames replace each other. Files in <filename>/etc</filename>
have the highest priority, files in <filename>/run</filename>
take precedence over files with the same name in
<filename>/usr/lib</filename>, and the content of
<envar>UDEV_HWDB_PATH</envar> comes last. This order can be
used to override a system-supplied hwdb file with a local file if needed;
a symlink in <filename>/etc</filename> with the same name as a hwdb file in
<filename>/usr/lib</filename>, pointing to <filename>/dev/null</filename>,
disables the hwdb file entirely. hwdb files must have the extension
<filename>.hwdb</filename>; other extensions are ignored.</para>
and any other directory in the <envar>UDEV_HWDB_PATH</envar> search path
variable. All hwdb files are collectively sorted and processed in
lexical order, regardless of the directories in which they live. However,
files with identical filenames replace each other. Files in
<filename>/etc</filename> have the highest priority, then files in
<filename>/run</filename>, <filename>/usr/lib</filename> and the ones in
<envar>UDEV_HWDB_PATH</envar> comes last. Files with higher priority
take precedence over files with the same name and lower priority.
This order can be used to override a system-supplied hwdb file with a
local file if needed; a symlink in <filename>/etc</filename> with the
same name as a hwdb file in <filename>/usr/lib</filename>, pointing to
<filename>/dev/null</filename>, disables the hwdb file entirely. hwdb
files must have the extension <filename>.hwdb</filename>; other
extensions are ignored.</para>
<para>The hwdb file contains data records consisting of matches and
associated key-value pairs. Every record in the hwdb starts with one or
@ -766,14 +767,17 @@
by <literal>=</literal>. An empty line signifies the end
of a record. Lines beginning with <literal>#</literal> are ignored.</para>
<para>The content of all hwdb files is read by
<citerefentry><refentrytitle>udevadm</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and compiled to a binary database located at <filename>/etc/udev/hwdb.bin</filename>,
or alternatively <filename>/usr/lib/udev/hwdb.bin</filename> if you want ship the compiled
If <envar>UDEV_HWDB_BIN</envar>
is set at run-time, and its value identifies a file in the file system, then the binary
database located under this name will be used.
During runtime only the binary database is used.</para>
<para>The content of all hwdb files is read by <citerefentry>
<refentrytitle>udevadm</refentrytitle><manvolnum>8</manvolnum>
</citerefentry> and compiled to a binary database located at
<filename>/etc/udev/hwdb.bin</filename>, or alternatively
<filename>/usr/lib/udev/hwdb.bin</filename>, if you want to ship the
compiled database in an immutable image by using <option>--usr</option>,
or anywhere on the system by using <option>--output</option>.
If <envar>UDEV_HWDB_BIN</envar> is set at run-time, and its value
identifies a file in the file system, then the binary database located
under this name will be used. During runtime only the binary database is
used.</para>
</refsect1>
<refsect1>