public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 1/2] docs: add further secure boot information, as in pve-docs
Date: Tue, 28 Nov 2023 14:35:08 +0100	[thread overview]
Message-ID: <20231128133509.118239-1-a.zeidler@proxmox.com> (raw)

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 docs/system-booting.rst | 21 ++++++++++++++++-----
 1 file changed, 16 insertions(+), 5 deletions(-)

diff --git a/docs/system-booting.rst b/docs/system-booting.rst
index 96c3458c..d4604e7d 100644
--- a/docs/system-booting.rst
+++ b/docs/system-booting.rst
@@ -8,8 +8,9 @@ Host Bootloader
 selected in the installer.
 
 For EFI Systems installed with ZFS as the root filesystem ``systemd-boot`` is
-used. All other deployments use the standard ``grub`` bootloader (this usually
-also applies to systems which are installed on top of Debian).
+used, unless Secure Boot is enabled. All other deployments use the standard
+``grub`` bootloader (this usually also applies to systems which are installed
+on top of Debian).
 
 
 .. _systembooting-installer-part-scheme:
@@ -30,9 +31,10 @@ The created partitions are:
   remaining space available for the chosen storage type
 
 Systems using ZFS as a root filesystem are booted with a kernel and initrd image
-stored on the 512 MB EFI System Partition. For legacy BIOS systems, ``grub`` is
-used, for EFI systems ``systemd-boot`` is used. Both are installed and configured
-to point to the ESPs.
+stored on the 512 MB EFI System Partition. For legacy BIOS systems, and EFI
+systems with Secure Boot enabled, ``grub`` is used, for EFI systems without
+Secure Boot, ``systemd-boot`` is used. Both are installed and configured to
+point to the ESPs.
 
 ``grub`` in BIOS mode (``--target i386-pc``) is installed onto the BIOS Boot
 Partition of all selected disks on all systems booted with ``grub`` (that is,
@@ -102,6 +104,15 @@ Proxmox Backup's kernel update synchronization mechanism, use the following:
 
   # proxmox-boot-tool init /dev/sda2
 
+or
+
+.. code-block:: console
+
+  # proxmox-boot-tool init /dev/sda2 grub
+
+to force initialization with Grub instead of systemd-boot, for example for
+Secure Boot support.
+
 Following this, `/etc/kernel/proxmox-boot-uuids`` should contain a new line with the
 UUID of the newly added partition. The ``init`` command will also automatically
 trigger a refresh of all configured ESPs.
-- 
2.39.2





             reply	other threads:[~2023-11-28 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 13:35 Alexander Zeidler [this message]
2023-11-28 13:35 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: remove pointless table title Alexander Zeidler
2023-11-29 13:08 ` [pbs-devel] applied: [PATCH proxmox-backup 1/2] docs: add further secure boot information, as in pve-docs 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=20231128133509.118239-1-a.zeidler@proxmox.com \
    --to=a.zeidler@proxmox.com \
    --cc=pbs-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal