From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH docs 3/7] installation: revise introduction
Date: Wed, 05 Mar 2025 09:35:04 +0100 [thread overview]
Message-ID: <D8870RJZ8THX.10OUIGE5N1G00@proxmox.com> (raw)
In-Reply-To: <20250304154101.3-4-a.zeidler@proxmox.com>
On Tue Mar 4, 2025 at 4:40 PM CET, Alexander Zeidler wrote:
> * Mention all currently available install options and link to them
> (interactive installer, unattended, on top of Debian)
> * Remove installer details and link to the installer, where the
> information will be included by a subsequent patch (
> "installer: revise introduction").
>
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
> pve-installation.adoc | 30 +++++++++++++++++-------------
> 1 file changed, 17 insertions(+), 13 deletions(-)
>
> diff --git a/pve-installation.adoc b/pve-installation.adoc
> index d320cfc..0065bca 100644
> --- a/pve-installation.adoc
> +++ b/pve-installation.adoc
> @@ -8,22 +8,24 @@ ifdef::wiki[]
> :title: Installation
> endif::wiki[]
>
> -{pve} is based on Debian. This is why the install disk images (ISO files)
> -provided by Proxmox include a complete Debian system as well as all necessary
> -{pve} packages.
> +Since {pve} is based on Debian GNU/Linux, the installer ISO files
> +provided by Proxmox include a complete Debian system as well as all
> +necessary {pve} packages.
>
> -TIP: See the xref:faq-support-table[support table in the FAQ] for the
> -relationship between {pve} releases and Debian releases.
> +{pve} can be installed via different methods:
>
> -The installer will guide you through the setup, allowing you to partition the
> -local disk(s), apply basic system configurations (for example, timezone,
> -language, network) and install all required packages. This process should not
> -take more than a few minutes. Installing with the provided ISO is the
> -recommended method for new and existing users.
> +* The recommended method is the creation of an
The recommended method is to create an..
would sound a bit less "biblical" to me ;)
> +xref:installation_prepare_media[installation medium], to boot the
> +convenient xref:installation_installer[interactive installer].
>
> -Alternatively, {pve} can be installed on top of an existing Debian system. This
> -option is only recommended for advanced users because detailed knowledge about
> -{pve} is required.
> +* As an alternative to the interactive installer, advanced users may
> +wish to xref:installation_unattended[install {pve} unattended].
> +
> +* With sufficient Debian and {pve} knowledge, you can also
> +xref:installation_on_debian[install {pve} on top of Debian] manually.
> +
> +TIP: See the xref:faq-support-table[support table in the FAQ] for the
> +relationship between {pve} releases and Debian releases.
>
> ifndef::wiki[]
>
> @@ -427,6 +429,8 @@ after a 10-second timeout.
> https://pve.proxmox.com/wiki/Automated_Installation[Visit our wiki] for more
> details and information on the unattended installation.
>
> +[[installation_on_debian]]
> +
> ifndef::wiki[]
>
> Install {pve} on Debian
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-05 8:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 15:40 [pve-devel] [PATCH v1 docs 0/7] Revise installation chapter Alexander Zeidler
2025-03-04 15:40 ` [pve-devel] [PATCH docs 1/7] system-requirements: revise subchapter and provide more details Alexander Zeidler
2025-03-04 16:21 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 2/7] installation: prepare medium: revise subchapter Alexander Zeidler
2025-03-04 16:34 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 3/7] installation: revise introduction Alexander Zeidler
2025-03-05 8:35 ` Shannon Sterz [this message]
2025-03-04 15:40 ` [pve-devel] [PATCH docs 4/7] installer: " Alexander Zeidler
2025-03-05 8:53 ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 5/7] installer: revise boot menu description and introduce sections Alexander Zeidler
2025-03-04 15:41 ` [pve-devel] [PATCH docs 6/7] installer: revise installation steps " Alexander Zeidler
2025-03-05 9:25 ` Shannon Sterz
2025-03-04 15:41 ` [pve-devel] [PATCH docs 7/7] installer: revise intro of advanced ZFS/BTRFS configuration options Alexander Zeidler
2025-03-05 9:27 ` Shannon Sterz
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=D8870RJZ8THX.10OUIGE5N1G00@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=pve-devel-bounces@lists.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal