diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-07-02 15:16:52 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2021-07-30 16:48:24 +0200 |
| commit | e5a8b4b593e7da1823f3258f7b4e7f2d370a7c3c (patch) | |
| tree | dde88b421577407040e97f72e2aa00c56f6f3d41 /man/bootctl.xml | |
| parent | 1f0fb7d544711248cba34615e43c5a76bc902d74 (diff) | |
| download | systemd-e5a8b4b593e7da1823f3258f7b4e7f2d370a7c3c.tar.gz | |
bootctl: tweak "bootctl update" to be a NOP when boot loader is already current and --graceful is given
Previously, the "bootctl update" logic would refrain from downrgading a
boot loader, but if the boot loader that is installed already matched
the version we could install we'd install it anyway, under the
assumption this was effectively without effect. This behaviour was handy
while developing boot loaders, since installing a modified boot loader
didn't require a version bump.
However, outside of the systems of boot loader developers I don't think
this behaviour makes much sense: we should always emphasize doing
minimal changes to the ESP, hence when an update is supposedly not
necessary, then don't do it. Only update if it really makes sense, to
minimize writes to the ESP. Updating the boot loader is a good thing
after all, but doing so redundantly is not.
Also, downgrade the message about this to LOG_NOTICE, given this
shouldn't be a reason to log.
Finally, exit cleanly in this cases (or if another boot loader is
detected)
Diffstat (limited to 'man/bootctl.xml')
| -rw-r--r-- | man/bootctl.xml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/man/bootctl.xml b/man/bootctl.xml index d05c3f34d0..a958cde7df 100644 --- a/man/bootctl.xml +++ b/man/bootctl.xml @@ -233,8 +233,9 @@ <varlistentry> <term><option>--graceful</option></term> - <listitem><para>Ignore failure when the EFI System Partition cannot be found, or when EFI variables - cannot be written. Currently only applies to random seed operations.</para></listitem> + <listitem><para>Ignore failure when the EFI System Partition cannot be found, when EFI variables + cannot be written, or a different or newer boot loader is already installed. Currently only applies + to random seed and update operations.</para></listitem> </varlistentry> <varlistentry> |