From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 0/3] network: update & reword
Date: Mon, 30 May 2022 14:53:25 +0200 [thread overview]
Message-ID: <00b0dab2-05d9-b746-f9dd-e49ed6e1fb54@proxmox.com> (raw)
In-Reply-To: <27f9614c-1f35-3496-0864-d6c57c27eb3e@proxmox.com>
On 5/30/22 14:50, Thomas Lamprecht wrote:
> Am 30/05/2022 um 14:40 schrieb Aaron Lauterer:
>> - ifupdown2 is default now, we can remove the install guide etc
>
> only for people coming from the PVE iso, but not for those installing PVE on top of
> a vanilla Debian installation. Albeit, one could argue that we could still remove
> it here and add a recommendation for installing ifupdown2 in the respective wiki[0].
Ah thanks. I'll reword it a bit and keep the install guide (maybe a bit shorter
as a note) for those people, just in case and update the wiki page as well.
>
> [0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye
prev parent reply other threads:[~2022-05-30 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 12:40 Aaron Lauterer
2022-05-30 12:40 ` [pve-devel] [PATCH docs 1/3] network: remove ifup ifdown as it won't reattach guests Aaron Lauterer
2022-05-30 12:40 ` [pve-devel] [PATCH docs 2/3] network: adapt apply config section to PVE 7 Aaron Lauterer
2022-05-30 12:40 ` [pve-devel] [PATCH docs 3/3] network: rework introduction for people with less experience Aaron Lauterer
2022-05-30 12:50 ` [pve-devel] [PATCH docs 0/3] network: update & reword Thomas Lamprecht
2022-05-30 12:53 ` Aaron Lauterer [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=00b0dab2-05d9-b746-f9dd-e49ed6e1fb54@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.