From: Christoph Heiss <c.heiss@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 2/2] docs: network-management: link to systemd.link documentation
Date: Tue, 12 Aug 2025 14:57:18 +0200 [thread overview]
Message-ID: <20250812125719.1301475-3-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250812125719.1301475-1-c.heiss@proxmox.com>
Might be useful for users, to get a quick overview of the syntax and
semantics of the options.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
docs/network-management.rst | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/docs/network-management.rst b/docs/network-management.rst
index f1dc4cc5..afbdb475 100644
--- a/docs/network-management.rst
+++ b/docs/network-management.rst
@@ -104,9 +104,9 @@ Overriding network device names
When upgrading kernels, adding PCIe devices or updating your BIOS, automatically
generated network interface names can change. To alleviate this issues, Proxmox
-Backup Server provides a tool for automatically generating .link files for
-overriding the name of network devices. It also automatically replaces the
-occurrences of the old interface name in ``/etc/network/interfaces``.
+Backup Server provides a tool for automatically generating `systemd .link`_
+files for overriding the name of network devices. It also automatically replaces
+the occurrences of the old interface name in ``/etc/network/interfaces``.
The generated link files are stored in ``/usr/local/lib/systemd/network``. For
the interfaces file a new file will be generated in the same place with a
@@ -151,3 +151,5 @@ interface should be pinned to:
In order to apply the changes made by ``proxmox-network-interface-pinning`` to
the network configuration, the host needs to be rebooted.
+
+.. _systemd .link: https://www.freedesktop.org/software/systemd/man/latest/systemd.link.html
--
2.50.1
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-08-12 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:57 [pbs-devel] [PATCH proxmox-backup 0/2] docs: network-management: improve pinning docs a bit Christoph Heiss
2025-08-12 12:57 ` [pbs-devel] [PATCH proxmox-backup 1/2] docs: network-management: use correct syntax for code-blocks Christoph Heiss
2025-08-12 12:57 ` Christoph Heiss [this message]
2025-08-12 13:48 ` [pbs-devel] [PATCH proxmox-backup 0/2] docs: network-management: improve pinning docs a bit Michael Köppl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250812125719.1301475-3-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox