Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-01-22 22:03:47 +03:00
Code Releases Activity

secure boot: fix typos, add inline code formatting

Browse Source 
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
This commit is contained in:
Alexander Zeidler 2023-11-28 14:56:28 +01:00 committed by Thomas Lamprecht
parent ea5fbb91ef
commit c1ffc4588a
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
system-booting.adoc
View File

@ -380,10 +380,11 @@ and integration in `proxmox-boot-tool`.
The following packages need to be installed for Secure Boot to be enabled: The following packages need to be installed for Secure Boot to be enabled:
- shim-signed (shim bootloader signed by Microsoft) - `shim-signed` (shim bootloader signed by Microsoft)
- shim-helpers-amd64-signed (fallback bootloader and MOKManager, signed by Proxmox) - `shim-helpers-amd64-signed` (fallback bootloader and MOKManager, signed by
- grub-efi-amd64-signed (Grub EFI bootloader, signed by Proxmox) Proxmox)
- proxmox-kernel-6.X.Y-Z-pve-signed (Kernel image, 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 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 pre-signed bootloader packages available. Any new installation of {pve} will
@ -419,7 +420,7 @@ To check the latter, run:
# findmnt / # 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`: should contain `zfs`:
---- ----
TARGET SOURCE FSTYPE OPTIONS 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. 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 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 on a disk, where the disk itself is not a boot option. If possible, try adding
disk as a boot option in the UEFI firmware setup utility and run the disk as a boot option in the UEFI firmware setup utility and run
`proxmox-boot-tool` again. `proxmox-boot-tool` again.
TIP: To enroll custom keys, see the accompanying TIP: To enroll custom keys, see the accompanying