From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs 1/3] fix #4847: network: extend section on interface naming scheme
Date: Fri, 17 Nov 2023 10:18:41 +0100 [thread overview]
Message-ID: <b5034f1d-ff56-4817-b365-135682be2b0b@proxmox.com> (raw)
In-Reply-To: <20230727103747.106574-2-f.weber@proxmox.com>
Am 27/07/2023 um 12:37 schrieb Friedrich Weber:
> Expand the existing section on systemd network interface names with a
> link to the systemd.net-naming-scheme(7) manpage and some information
> about naming scheme versions. Also mention the possibility of
> interface naming changes due to a new naming scheme version, or
> kernel/driver updates. This happens for quite some users during the
> upgrade from PVE 7 to 8.
>
> Further, describe how to pin a specific naming scheme version and how
> to override interface names using systemd.link files.
>
> Also, make some formatting fixes to the existing text.
>
> Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
> ---
> pve-network.adoc | 122 +++++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 107 insertions(+), 15 deletions(-)
>
>
applied this one for now, thanks!
next prev parent reply other threads:[~2023-11-17 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 10:37 [pve-devel] [PATCH+RFC docs/common 0/3] fix #4847: network: custom naming for network devices Friedrich Weber
2023-07-27 10:37 ` [pve-devel] [PATCH docs 1/3] fix #4847: network: extend section on interface naming scheme Friedrich Weber
2023-11-17 9:18 ` Thomas Lamprecht [this message]
2023-07-27 10:37 ` [pve-devel] [RFC docs 2/3] network: describe and recommend `c*` names for custom interface Friedrich Weber
2023-07-27 10:37 ` [pve-devel] [RFC common 3/3] network: recognize interfaces matching `c*` as physical NICs Friedrich Weber
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=b5034f1d-ff56-4817-b365-135682be2b0b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.weber@proxmox.com \
--cc=pve-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