From: Matthias Heiserer <m.heiserer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 05/10] move installation options to advanced folder
Date: Wed, 9 Nov 2022 12:58:23 +0100 [thread overview]
Message-ID: <20221109115828.137770-6-m.heiserer@proxmox.com> (raw)
In-Reply-To: <20221109115828.137770-1-m.heiserer@proxmox.com>
@Thomas The screenshot still shows the PVE6 menu.
Do you want to update that yourself, or should I send you the up-to-date screeshot?
Signed-off-by: Matthias Heiserer <m.heiserer@proxmox.com>
---
pve-installation.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index 8de6ac9..c86b620 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -75,7 +75,7 @@ TIP: It's possible to use the installation wizard with a keyboard only. Buttons
can be clicked by pressing the `ALT` key combined with the underlined character
from the respective button. For example, `ALT + N` to press a `Next` button.
-Install {pve} (Debug mode)::
+Advanced Options: Install {pve} (Debug mode)::
Starts the installation in debug mode. A console will be opened at several
installation steps. This helps to debug the situation if something goes wrong.
@@ -84,7 +84,7 @@ system with all basic tools available. You can use it, for example, to
xref:chapter_zfs[repair a degraded ZFS 'rpool'] or fix the
xref:sysboot[bootloader] for an existing {pve} setup.
-Rescue Boot::
+Advanced Options: Rescue Boot::
With this option you can boot an existing installation. It searches all attached
hard disks. If it finds an existing installation, it boots directly into that
@@ -92,7 +92,7 @@ disk using the Linux kernel from the ISO. This can be useful if there are
problems with the boot block (grub) or the BIOS is unable to read the boot block
from the disk.
-Test Memory::
+Advanced Options: Test Memory::
Runs `memtest86+`. This is useful to check if the memory is functional and free
of errors.
--
2.30.2
next prev parent reply other threads:[~2022-11-09 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 11:58 [pve-devel] [PATCH docs 00/10] docs (mostly) spelling update Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 01/10] consistently use 'web interface' (two words) Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 02/10] remove misplaced comma Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 03/10] consistently capitalize Ceph Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 04/10] add note that secure boot needs to be disabled for host installation Matthias Heiserer
2022-11-09 11:58 ` Matthias Heiserer [this message]
2022-11-09 14:46 ` [pve-devel] [PATCH docs 05/10] move installation options to advanced folder Thomas Lamprecht
2022-11-09 11:58 ` [pve-devel] [PATCH docs 06/10] add missing comma in if sentences Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 07/10] rephrase when root password is set to make it clear that when logging it, it is already set Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 08/10] add missing letter Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 09/10] it's -> its because it isn't 'it is' Matthias Heiserer
2022-11-09 11:58 ` [pve-devel] [PATCH docs 10/10] update link to debian handbook. current one is 404 Matthias Heiserer
2022-11-09 14:51 ` [pve-devel] applied-series: [PATCH docs 00/10] docs (mostly) spelling update 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=20221109115828.137770-6-m.heiserer@proxmox.com \
--to=m.heiserer@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