From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] firmware-updates: replace dameon.conf with fwupd.conf
Date: Mon, 29 Dec 2025 14:39:18 +0100 [thread overview]
Message-ID: <20251229133920.40752-1-m.sandoval@proxmox.com> (raw)
This was changed in [7fa42274], which first appeared in fwupd [1.9.1].
For reference, the latest version in Bookworm is 1.8.12 and in Trixie
the currently available version is 2.0.8.
[7fa42274] https://github.com/fwupd/fwupd/commit/7fa422744c42d5f6a207d43c094d02dece64baf6
[1.9.1] https://github.com/fwupd/fwupd/releases/tag/1.9.1
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
firmware-updates.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/firmware-updates.adoc b/firmware-updates.adoc
index ea31dac..9ca4b6e 100644
--- a/firmware-updates.adoc
+++ b/firmware-updates.adoc
@@ -53,9 +53,9 @@ booted via UEFI.
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:
+mount point of the EFI partition in `/etc/fwupd/fwupd.conf`, for example:
-.File `/etc/fwupd/daemon.conf`
+.File `/etc/fwupd/fwupd.conf`
----
# Override the location used for the EFI system partition (ESP) path.
EspLocation=/boot/efi
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-12-29 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 13:39 Maximiliano Sandoval [this message]
2025-12-29 13:39 ` [pve-devel] [PATCH docs 2/2] firmware-updates: add group header to fwupd.conf 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=20251229133920.40752-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.