From: John Crisp <jcrisp@safeandsoundit.co.uk>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Any plans to migrate to systemd-networkd?
Date: Fri, 04 Oct 2024 01:03:40 +0200 [thread overview]
Message-ID: <BCC47C94-1615-4545-9343-CFD82B267EA6@safeandsoundit.co.uk> (raw)
In-Reply-To: <CAO6gj48wmVVkKnAe1Yt3gpvfcZ+R+v7wcwovGvNYEmo1ud_e9w@mail.gmail.com>
On 4 October 2024 00:10:45 CEST, Kyle Schmitt <kyleaschmitt@gmail.com> wrote:
>For an alternate point of view, unless does away with support for
>everything other systemd-networkd, please don't change. Dealing with my
>production systems, most of these systemd changes feel like change for
>change's sake, not progress. And I haven't had pleasant experiences with
>systemd-networkd in production environments.
+1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2024-10-03 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78619bca-8468-43e7-a67e-00f82f6c9cd7@gmail.com>
2024-10-03 22:10 ` Kyle Schmitt
2024-10-03 23:03 ` John Crisp [this message]
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=BCC47C94-1615-4545-9343-CFD82B267EA6@safeandsoundit.co.uk \
--to=jcrisp@safeandsoundit.co.uk \
--cc=pve-user@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