From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] secure boot: fix typos, add inline code formatting
Date: Tue, 28 Nov 2023 14:56:28 +0100 [thread overview]
Message-ID: <20231128135629.123748-1-a.zeidler@proxmox.com> (raw)
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
next reply other threads:[~2023-11-28 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 13:56 Alexander Zeidler [this message]
2023-11-28 13:56 ` [pve-devel] [PATCH docs 2/2] installation: be more specific about current secure boot state Alexander Zeidler
2023-11-28 15:18 ` [pve-devel] applied: [PATCH docs 1/2] secure boot: fix typos, add inline code formatting 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=20231128135629.123748-1-a.zeidler@proxmox.com \
--to=a.zeidler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.