From a54ac63bbf9b2c71026ac9028a8ffaf186cf3c82 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Sun, 28 Jun 2020 18:58:14 +0200 Subject: New upstream version 1.25.90 --- docs/api/html/nm-initrd-generator.html | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) (limited to 'docs/api/html/nm-initrd-generator.html') diff --git a/docs/api/html/nm-initrd-generator.html b/docs/api/html/nm-initrd-generator.html index 8e17d821..23b00eb1 100644 --- a/docs/api/html/nm-initrd-generator.html +++ b/docs/api/html/nm-initrd-generator.html @@ -54,6 +54,13 @@

Output connection directory.

+

+ -i | --initrd-data-dir + path +

+

Output directory for initrd data (e.g. hostname).

+ +

-d | --sysfs-dir path @@ -81,6 +88,7 @@ nameserver rd.peerdns rd.bootif +rd.net.timeout.dhcp BOOTIF

Please consult the dracut.cmdline(7) @@ -91,6 +99,26 @@

+

Differences from the network-legacy dracut module

+

nm-initrd-generator generates a set of + connections that are then configured by the NetworkManager + instance running in the initrd. There are some differences in + behavior compared to the network-legacy dracut module:

+
    +
  • When an interface is configured with a static address + and a gateway, the network-legacy module waits that the + gateway responds to arping requests before proceeding, while + NetworkManager doesn't.

  • +
  • network-legacy configures interfaces one by one in the + order in which they are announced by udev. If multiple + interfaces specify a hostname (from command line or from + DHCP), the one from the last interface activated wins. With + NetworkManager, hostnames from command line have higher + precedence over ones from DHCP, and the last that appears in + the command line wins.

  • +
+
+

Exit Status

nm-initrd-generator exits with status 0. It ignores unrecognized options and prints an error message if it encounters a malformed option.

-- cgit 1.3.0-6-gf8a5