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 --- man/nm-initrd-generator.xml | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) (limited to 'man/nm-initrd-generator.xml') diff --git a/man/nm-initrd-generator.xml b/man/nm-initrd-generator.xml index df2cf12a..37f5ffdf 100644 --- a/man/nm-initrd-generator.xml +++ b/man/nm-initrd-generator.xml @@ -74,6 +74,20 @@ + + + + + + + path + + + + Output directory for initrd data (e.g. hostname). + + + @@ -118,6 +132,7 @@ + @@ -128,6 +143,34 @@ + 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