From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 0/5] installation and system improvements
Date: Thu, 25 Jan 2024 12:06:26 +0100 [thread overview]
Message-ID: <20240125110646.427124-1-c.heiss@proxmox.com> (raw)
This mainly updates the installation section, to bring it up-to-date
with the latest available installer ISO.
v1: https://lists.proxmox.com/pipermail/pve-devel/2023-November/060814.html
Changes v1 -> v2:
* rebased on lastest master
* dropped two obsolete patches
Christoph Heiss (5):
screenshots: update grub menu screenshot
installation: update installer option wording & description
installation: add note about memtest86+ incompatibility with
secureboot
installation: add section about booting with `nomodeset`
tree-wide: unify spelling of GRUB and systemd-boot
images/screenshot/pve-grub-menu.png | Bin 66997 -> 66784 bytes
images/screenshot/pve-grub-menu.ppm | Bin 2362384 -> 2359312 bytes
local-zfs.adoc | 23 +++++++--------
pve-installation.adoc | 41 ++++++++++++++++++--------
system-booting.adoc | 44 ++++++++++++++--------------
5 files changed, 62 insertions(+), 46 deletions(-)
--
2.42.0
next reply other threads:[~2024-01-25 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 11:06 Christoph Heiss [this message]
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 1/5] screenshots: update grub menu screenshot Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 2/5] installation: update installer option wording & description Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 3/5] installation: add note about memtest86+ incompatibility with secureboot Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 4/5] installation: add section about booting with `nomodeset` Christoph Heiss
2024-01-25 11:06 ` [pve-devel] [PATCH docs v2 5/5] tree-wide: unify spelling of GRUB and systemd-boot Christoph Heiss
2024-02-20 14:46 ` [pve-devel] applied-series: [PATCH docs v2 0/5] installation and system improvements Thomas Lamprecht
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=20240125110646.427124-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