From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH docs v2] firmware-updates: remove documentation regarding fwdup's config
Date: Mon, 16 Mar 2026 16:49:06 +0100 [thread overview]
Message-ID: <20260316154907.536042-1-m.sandoval@proxmox.com> (raw)
As a side note regarding daemon.conf, fwupd since Trixie stores its
config at /etc/fwupd/fwupd.conf. This was changed in [7fa42274], which
first appeared in fwupd [1.9.1].
[7fa42274] https://github.com/fwupd/fwupd/commit/7fa422744c42d5f6a207d43c094d02dece64baf6
[1.9.1] https://github.com/fwupd/fwupd/releases/tag/1.9.1
[#8945] https://github.com/fwupd/fwupd/issues/8945#issuecomment-2993821262
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
firmware-updates.adoc | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/firmware-updates.adoc b/firmware-updates.adoc
index ea31dac..d9025d4 100644
--- a/firmware-updates.adoc
+++ b/firmware-updates.adoc
@@ -52,14 +52,7 @@ booted via UEFI.
{pve} ships its own version of the `fwupd` package to enable Secure Boot
Support with the Proxmox signing key. This package consciously dropped the
dependency recommendation for the `udisks2` package, due to observed issues with
-its use on hypervisors. That means you must explicitly configure the correct
-mount point of the EFI partition in `/etc/fwupd/daemon.conf`, for example:
-
-.File `/etc/fwupd/daemon.conf`
-----
-# Override the location used for the EFI system partition (ESP) path.
-EspLocation=/boot/efi
-----
+its use on hypervisors.
TIP: If the update instructions require a host reboot, make sure that it can be
done safely. See also xref:ha_manager_node_maintenance[Node Maintenance].
--
2.47.3
next reply other threads:[~2026-03-16 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 15:49 Maximiliano Sandoval [this message]
2026-03-16 15:50 ` Maximiliano Sandoval
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=20260316154907.536042-1-m.sandoval@proxmox.com \
--to=m.sandoval@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.