]> git.ipfire.org Git - thirdparty/systemd.git/commit
networkd: call networkd a "network management" rather "network configuration" tool
authorLennart Poettering <lennart@poettering.net>
Mon, 20 Oct 2025 10:59:32 +0000 (12:59 +0200)
committerLennart Poettering <lennart@poettering.net>
Mon, 20 Oct 2025 16:17:29 +0000 (18:17 +0200)
commit1f3f40f0ff2a57428df1466689115470ca99ea5e
treeb40ccb079db16d7258ca82a0b0fa2dce9e51872a
parentcbbc7e51ec0b4e8a421672f6117483bdea4ae69c
networkd: call networkd a "network management" rather "network configuration" tool

This has irked me for a while. For me network configuration is the stuff
we store on disk in configuration file. And networkd then *applies* the
configuration. But the units so far claimed that networkd was the
"configuration" itself. Which I guess might make sense to some, but to
me sounds a bit unprecise. Let's clean this up, and call what networkd
is doing "Network Management".
units/systemd-networkd-varlink.socket
units/systemd-networkd-wait-online.service.in
units/systemd-networkd-wait-online@.service.in
units/systemd-networkd.service.in
units/systemd-networkd.socket