[pve-devel] [PATCH docs 1/2] secure boot: fix typos, add inline code formatting

[pve-devel] [PATCH docs 1/2] secure boot: fix typos, add inline code formatting

[Alexander Zeidler]

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 system-booting.adoc | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/system-booting.adoc b/system-booting.adoc
index c8761a4..af56225 100644
--- a/system-booting.adoc
+++ b/system-booting.adoc
@@ -380,10 +380,11 @@ and integration in `proxmox-boot-tool`.
 
 The following packages need to be installed for Secure Boot to be enabled:
 
-- shim-signed (shim bootloader signed by Microsoft)
-- shim-helpers-amd64-signed (fallback bootloader and MOKManager, signed by Proxmox)
-- grub-efi-amd64-signed (Grub EFI bootloader, signed by Proxmox)
-- proxmox-kernel-6.X.Y-Z-pve-signed (Kernel image, signed by Proxmox)
+- `shim-signed` (shim bootloader signed by Microsoft)
+- `shim-helpers-amd64-signed` (fallback bootloader and MOKManager, signed by
+  Proxmox)
+- `grub-efi-amd64-signed` (Grub EFI bootloader, signed by Proxmox)
+- `proxmox-kernel-6.X.Y-Z-pve-signed` (Kernel image, signed by Proxmox)
 
 Only Grub as bootloader is supported out of the box, since there are no other
 pre-signed bootloader packages available. Any new installation of {pve} will
@@ -419,7 +420,7 @@ To check the latter, run:
 # findmnt /
 ----
 
-If the host is indeed running using ZFS as root filesystem, the `FSTYPE` column
+If the host is indeed using ZFS as root filesystem, the `FSTYPE` column
 should contain `zfs`:
 ----
 TARGET SOURCE           FSTYPE OPTIONS
@@ -485,8 +486,8 @@ can try adding it manually (if supported by the firmware), by adding the file
 
 NOTE: Some UEFI firmwares are known to drop the `proxmox` boot option on reboot.
 This can happen if the `proxmox` boot entry is pointing to a Grub installation
-on a disk, where the disk itself not a boot option. If possible, try adding the
-disk as a boot option in the UEFI firmware setup utility and run
+on a disk, where the disk itself is not a boot option. If possible, try adding
+the disk as a boot option in the UEFI firmware setup utility and run
 `proxmox-boot-tool` again.
 
 TIP: To enroll custom keys, see the accompanying
-- 
2.39.2

[pve-devel] [PATCH docs 2/2] installation: be more specific about current secure boot state

[Alexander Zeidler]

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 pve-installation.adoc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pve-installation.adoc b/pve-installation.adoc
index 44b59c0..1e909e2 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -60,7 +60,8 @@ Please insert the xref:installation_prepare_media[prepared installation media]
 (for example, USB flash drive or CD-ROM) and boot from it.
 
 TIP: Make sure that booting from the installation medium (for example, USB) is
-enabled in your servers firmware settings and secure boot is disabled.
+enabled in your server's firmware settings. Secure boot needs to be disabled
+when booting an installer prior to {pve} version 8.1.
 
 [thumbnail="screenshot/pve-grub-menu.png"]
 
-- 
2.39.2

[pve-devel] applied: [PATCH docs 1/2] secure boot: fix typos, add inline code formatting

[Thomas Lamprecht]

Am 28/11/2023 um 14:56 schrieb Alexander Zeidler:
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
> ---
>  system-booting.adoc | 15 ++++++++-------
>  1 file changed, 8 insertions(+), 7 deletions(-)
> 
>

applied series, thanks!