public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH pve-docs 1/1] network: update name of pinning tool
@ 2025-08-05 12:26 Stefan Hanreich
  2025-08-05 13:35 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Stefan Hanreich @ 2025-08-05 12:26 UTC (permalink / raw)
  To: pve-devel

Has been changed from proxmox-network-interface-pinning to
pve-network-interface-pinning for the initial release, since we do not
include the standalone rust tool for now.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 pve-network.adoc | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/pve-network.adoc b/pve-network.adoc
index 289d6ad..a46ce0e 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -158,8 +158,8 @@ command line. You need to reboot for the changes to take effect.
 Overriding network device names
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Using the proxmox-network-interface-pinning Tool
-++++++++++++++++++++++++++++++++++++++++++++++++
+Using the pve-network-interface-pinning Tool
+++++++++++++++++++++++++++++++++++++++++++++
 
 Proxmox VE provides a tool for automatically generating .link files for
 overriding the name of network devices. It also automatically replaces the
@@ -193,29 +193,29 @@ configuration files (see above). The generated names will use the default prefix
 `nic`, so the resulting interface names will be `nic1`, `nic2`, ...
 
 ----
-proxmox-network-interface-pinning generate
+pve-network-interface-pinning generate
 ----
 
 You can override the default prefix with the `--prefix` flag:
 
 ----
-proxmox-network-interface-pinning generate --prefix myprefix
+pve-network-interface-pinning generate --prefix myprefix
 ----
 
 It is also possible to pin only a specific interface:
 
 ----
-proxmox-network-interface-pinning generate --interface enp1s0
+pve-network-interface-pinning generate --interface enp1s0
 ----
 
 When pinning a specific interface, you can specify the exact name that the
 interface should be pinned to:
 
 ----
-proxmox-network-interface-pinning generate --interface enp1s0 --target-name if42
+pve-network-interface-pinning generate --interface enp1s0 --target-name if42
 ----
 
-In order to apply the changes made by `proxmox-network-interface-pinning` to the
+In order to apply the changes made by `pve-network-interface-pinning` to the
 network configuration, the node needs to be rebooted.
 
 
-- 
2.47.2


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH pve-docs 1/1] network: update name of pinning tool
  2025-08-05 12:26 [pve-devel] [PATCH pve-docs 1/1] network: update name of pinning tool Stefan Hanreich
@ 2025-08-05 13:35 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2025-08-05 13:35 UTC (permalink / raw)
  To: pve-devel, Stefan Hanreich

On Tue, 05 Aug 2025 14:26:58 +0200, Stefan Hanreich wrote:
> Has been changed from proxmox-network-interface-pinning to
> pve-network-interface-pinning for the initial release, since we do not
> include the standalone rust tool for now.
> 
> 

Applied, thanks!

[1/1] network: update name of pinning tool
      commit: 3f1bf7305d4149682b37fba9c42f816f17920261


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-08-05 13:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-08-05 12:26 [pve-devel] [PATCH pve-docs 1/1] network: update name of pinning tool Stefan Hanreich
2025-08-05 13:35 ` [pve-devel] applied: " Thomas Lamprecht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal