From 32e276708089110243682d8aaa3d58075b91f0d6 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 23 Sep 2022 14:59:02 +0200 Subject: tree-wide: use the term "initrd" at most places we so far used "initramfs" In most cases we refernced the concept as "initrd". Let's convert most remaining uses of "initramfs" to "initrd" too, to stay internally consistent. This leaves "initramfs" only where it's relevant to explain historical concepts or where "initramfs" is part of the API (i.e. in /run/initramfs). Follow-up for: b66a6e1a5838b874b789820c090dd6850cf10513 --- man/systemd-networkd.service.xml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'man/systemd-networkd.service.xml') diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml index df6e180ffc..12cd4c331b 100644 --- a/man/systemd-networkd.service.xml +++ b/man/systemd-networkd.service.xml @@ -54,13 +54,11 @@ systemd.network5. - When systemd-networkd exits, it generally leaves - existing network devices and configuration intact. This makes it possible to - transition from the initramfs and to restart the service without breaking - connectivity. This also means that when configuration is updated and - systemd-networkd is restarted, netdev interfaces for - which configuration was removed will not be dropped, and may need to be - cleaned up manually. + When systemd-networkd exits, it generally leaves existing network devices and + configuration intact. This makes it possible to transition from the initrd and to restart the service + without breaking connectivity. This also means that when configuration is updated and + systemd-networkd is restarted, netdev interfaces for which configuration was removed + will not be dropped, and may need to be cleaned up manually. systemd-networkd may be introspected and controlled at runtime using networkctl1. -- cgit v1.2.1