summaryrefslogtreecommitdiffstats
path: root/man/systemd-networkd.service.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-09-23 14:59:02 +0200
committerLennart Poettering <lennart@poettering.net>2022-09-23 15:10:53 +0200
commit32e276708089110243682d8aaa3d58075b91f0d6 (patch)
tree44a32b969266f7dfe9529f31e79046e78ca7e474 /man/systemd-networkd.service.xml
parentMerge pull request #24686 from d4nuu8/delta_output (diff)
downloadsystemd-32e276708089110243682d8aaa3d58075b91f0d6.tar.xz
systemd-32e276708089110243682d8aaa3d58075b91f0d6.zip
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
Diffstat (limited to 'man/systemd-networkd.service.xml')
-rw-r--r--man/systemd-networkd.service.xml12
1 files changed, 5 insertions, 7 deletions
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 @@
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
- <para>When <filename>systemd-networkd</filename> 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
- <filename>systemd-networkd</filename> is restarted, netdev interfaces for
- which configuration was removed will not be dropped, and may need to be
- cleaned up manually.</para>
+ <para>When <filename>systemd-networkd</filename> 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
+ <filename>systemd-networkd</filename> is restarted, netdev interfaces for which configuration was removed
+ will not be dropped, and may need to be cleaned up manually.</para>
<para><command>systemd-networkd</command> may be introspected and controlled at runtime using
<citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.