summaryrefslogtreecommitdiff
path: root/man/loader.conf.xml
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2022-03-16 12:01:37 +0100
committerLennart Poettering <lennart@poettering.net>2022-03-16 18:39:57 +0100
commitdeb5c820cadb970039509b9acef31f23216c00cc (patch)
tree5c2aa55396d10db57b99a5cdbbf5f3ff4110fa73 /man/loader.conf.xml
parentc2c7eea1e9153d2f86c403f8c0b1df98b604caae (diff)
downloadsystemd-deb5c820cadb970039509b9acef31f23216c00cc.tar.gz
sd-boot: disable bitlocker reboot feature for now
Conceptually the feature is great and should exist, but in its current form should be worked to be generic (i.e. not specific to Windows/Bitlocker, but appliable to any boot entry), not be global (but be a per-entry thing), not require a BootXXXX entry to exist, and not check for the BitLocker signature (as TPMs are not just used for BitLocker). Since we want to get 251 released, mark it in the documentation, in NEWS and in code as experimental and make clear it will be reworked in a future release. Also, make it opt-in to make it less likely people come to rely on it without reading up on it, and understanding that it will likely change sooner or later. Follow-up for: #22043 See: #22390
Diffstat (limited to 'man/loader.conf.xml')
-rw-r--r--man/loader.conf.xml7
1 files changed, 5 insertions, 2 deletions
diff --git a/man/loader.conf.xml b/man/loader.conf.xml
index caff44aa1e..e5453c7dcd 100644
--- a/man/loader.conf.xml
+++ b/man/loader.conf.xml
@@ -206,8 +206,11 @@
<varlistentry>
<term>reboot-for-bitlocker</term>
- <listitem><para>Work around BitLocker requiring a recovery key when the boot loader was
- updated (enabled by default).</para>
+ <listitem><para>Caveat: This feature is experimental, and is likely to be changed (or removed in its
+ current form) in a future version of systemd.</para>
+
+ <para>Work around BitLocker requiring a recovery key when the boot loader was
+ updated (disabled by default).</para>
<para>Try to detect BitLocker encrypted drives along with an active TPM. If both are found
and Windows Boot Manager is selected in the boot menu, set the <literal>BootNext</literal>