X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fudev.xml;h=bd071e17709414db21e51e51ea657f269b6acb10;hp=022072514082bfa11fa649ff92490788c5ee0af8;hb=b408e2a8be6b87fd1796c45a767d00bbb00d7148;hpb=fbce11397f4d19821a9dfe66ee3ebe11cad90057
diff --git a/man/udev.xml b/man/udev.xml
index 022072514..bd071e177 100644
--- a/man/udev.xml
+++ b/man/udev.xml
@@ -340,6 +340,13 @@
+
+ SECLABEL{module}
+
+ Applies the specified Linux Security Module label to the device node.
+
+
+
ATTR{key}
@@ -704,15 +711,15 @@
system hwdb directory /usr/lib/udev/hwdb.d,
the volatile runtime directory /run/udev/hwdb.d
and the local administration directory /etc/udev/hwdb.d.
- All rules files are collectively sorted and processed in lexical order,
+ 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 /lib. This 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 rules file in
+ a symlink in /etc with the same name as a hwdb file in
/lib, pointing to /dev/null,
- disables the rules file entirely. hwdb files must have the extension
+ disables the hwdb file entirely. hwdb files must have the extension
.hwdb; other extensions are ignored.
The hwdb file contains data records consisting of matches and
@@ -734,6 +741,203 @@
During runtime only the binary database is used.
+ Network Link Configuration
+ Network link configuration is performed by the net_setup_link
+ udev builtin.
+
+ The link files are read from the files located in the
+ system network directory /usr/lib/systemd/network,
+ the volatile runtime network directory /run/systemd/network
+ and the local administration network directory /etc/systemd/network.
+ Link files must have the extension .link; other extensions are ignored.
+ All link 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 /lib. This can be
+ used to override a system-supplied link file with a local file if needed;
+ a symlink in /etc with the same name as a link file in
+ /lib, pointing to /dev/null,
+ disables the link file entirely.
+
+ The link file contains a [Match] section, which
+ determines if a given link file may be applied to a given device; and a
+ [Link] section specifying how the device should be
+ configured. The first (in lexical order) of the link files that matches
+ a given device is applied.
+
+ A link file is said to match a device if each of the entries in the
+ [Match] section matches, or if the section is empty.
+ The following keys are accepted:
+
+
+
+ MACAddress
+
+ The hardware address.
+
+
+
+
+ Path
+
+ The persistent path, as exposed by the udev property ID_PATH.
+
+
+
+ Driver
+
+ The driver currently bound to the device, as exposed by the udev property DRIVER.
+
+
+
+ Type
+
+ The device type, as exposed by the udev property DEVTYPE.
+
+
+
+
+ The [Link] section accepts the following keys:
+
+
+
+ Description
+
+ A description of the device.
+
+
+
+ Alias
+
+ The ifalias is set to this value.
+
+
+
+ MACAddressPolicy
+
+ The policy by which the MAC address should be set. The available policies are:
+
+
+ persistent
+
+ If the hardware has a persistent MAC address, as most hardware should, and this is used by
+ the kernel, nothing is done. Otherwise, a new MAC address is generated which is guaranteed to be
+ the same on every boot for the given machine and the given device, but which is otherwise random.
+
+
+
+
+ random
+
+ If the kernel is using a random MAC address, nothing is done. Otherwise, a new address is
+ randomly generated each time the device appears, typically at boot.
+
+
+
+
+
+
+ MACAddress
+
+ The MAC address to use, if no MACAddressPolicy is specified.
+
+
+
+ NamePolicy
+
+ An ordered, space-separated list of policies by which the interface name should be set.
+ NamePolicy may be disabeld by specifying net.ifnames=0 on the
+ kernel commandline. Each of the policies may fail, and the first successfull one is used. The name
+ is not set directly, but exported to udev as the property ID_NET_NAME, which is
+ by default used by an udev rule to set NAME. The available policies are:
+
+
+ onboard
+
+ The name is set based on information given by the firmware for on-board devices, as
+ exported by the udev property ID_NET_NAME_ONBOARD.
+
+
+
+ slot
+
+ The name is set based on information given by the firmware for hot-plug devices, as
+ exported by the udev property ID_NET_NAME_SLOT.
+
+
+
+ path
+
+ The name is set based on the device's physical location, as exported by the udev
+ property ID_NET_NAME_PATH.
+
+
+
+ mac
+
+ The name is set based on the device's persistent MAC address, as exported by the udev
+ property ID_NET_NAME_MAC.
+
+
+
+
+
+
+ Name
+
+ The interface name to use in case all the policies specified in NamePolicy
+ fail, or in case NamePolicy is missing or disabled.
+
+
+
+ MTU
+
+ The MTU to set for the device.
+
+
+
+ SpeedMBytes
+
+ The speed to set for the device.
+
+
+
+ Duplex
+
+ The duplex mode to set for the device. The accepted values are half and
+ full.
+
+
+
+ WakeOnLan
+
+ The Wake-On-Lan policy to set for the device. The supported values are:
+
+
+ phy
+
+ Wake on PHY activity.
+
+
+
+ magic
+
+ Wake on receipt of magic packet.
+
+
+
+ off
+
+ Never wake.
+
+
+
+
+
+
+
+
See Also