Hence, with this new Property= field you can nicely define via .link files which network service shall manage the matching devices.
This is particularly useful as systemd out-of-the-box ships with a bunch of .link files that match devices created by systemd-nspawn, systemd-vmspawn and systemd-nsresourced. These .link files have been updated to clearly indicate that these interfaces are supposed to be managed by networkd, and nothing else.
Lennart Poettering /
npub1rk…qzenj
2024-05-07 07:43:48
in reply to nevent1q…ss3v
Author Public Key
npub1rk2uxtv6nk262nucavh259t085a8rhzfaj3vjc9jhzvkyav0rnqqxqzenjPublished at
2024-05-07 07:43:48Event JSON
{
"id": "a8977664fbde38b7de686d6fe93e3c9e82538e0401f522927dde3c98d9278192",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1715067828,
"kind": 1,
"tags": [
[
"e",
"f7a4cfbfc5929914ed1f3368feadea0b791833107f5162fb508f550f5f90ae65",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/112398685180374949",
"activitypub"
]
],
"content": "Hence, with this new Property= field you can nicely define via .link files which network service shall manage the matching devices.\n\nThis is particularly useful as systemd out-of-the-box ships with a bunch of .link files that match devices created by systemd-nspawn, systemd-vmspawn and systemd-nsresourced. These .link files have been updated to clearly indicate that these interfaces are supposed to be managed by networkd, and nothing else.",
"sig": "af875190fde67d21c1ff0950a14e168adc5e8e31887dc73bead4fde95c9a86631ab0d7bfb234820e3e994f9f5d7db8c8a04630581f85ef2bc19a448af187a7e4"
}