public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 0/5] improve & unify installation(-related) documentation
Date: Mon, 11 Mar 2024 13:29:06 +0100	[thread overview]
Message-ID: <20240311122938.565228-1-c.heiss@proxmox.com> (raw)

This series in short tries to bring the documentation for the
ISO installation flow and anything related to it in line the with
respective documentation for PMG. As both products use the same
installer (minus small differences such as LVM options and BTRFS
support) and overall same basic system setup, it is worth unifying them.

There is (of course) still room for improvement, esp. regarding the apt
repo/update section as pointed out by Alex. Still like to get this in
rather sooner than later, to not diverge even more.

I'll send the appropriate pmg-docs series (see v1 of that [0]) when this
has been finalized & applied, to keep it transparent and easier to
reason about.

[0] https://lists.proxmox.com/pipermail/pmg-devel/2024-March/002870.html

Revision history
----------------
v1: https://lists.proxmox.com/pipermail/pve-devel/2024-March/062056.html

Notable changes v1 -> v2:
  * dropped already-applied patches
  * slight rewording in some places based on suggestions

Christoph Heiss (5):
  package-repos: improve wording partly based on pmg-docs
  installation: iso: improve & align wording with pmg-docs
  installation: lvm-options: improve & align wording with pmg-docs
  installation: zfs-options: improve & align wording with pmg-docs
  installation: iso: reflow location and password dialog screenshots

 pve-installation.adoc  | 144 ++++++++++++++++++++++++++---------------
 pve-package-repos.adoc |  26 ++++----
 2 files changed, 107 insertions(+), 63 deletions(-)

--
2.43.0





             reply	other threads:[~2024-03-11 12:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 12:29 Christoph Heiss [this message]
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 1/5] package-repos: improve wording partly based on pmg-docs Christoph Heiss
2024-03-11 14:10   ` Stefan Sterz
2024-03-12  8:47     ` Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 2/5] installation: iso: improve & align wording with pmg-docs Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 3/5] installation: lvm-options: " Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 4/5] installation: zfs-options: " Christoph Heiss
2024-03-11 12:29 ` [pve-devel] [PATCH docs v2 5/5] installation: iso: reflow location and password dialog screenshots Christoph Heiss
2024-03-21 15:30 ` [pve-devel] [PATCH docs v2 0/5] improve & unify installation(-related) documentation Christoph Heiss

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=20240311122938.565228-1-c.heiss@proxmox.com \
    --to=c.heiss@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