On 31/12/2024 18:43, Nicolas George wrote:
Max Nikulin (12024-12-31):
Are you sure that fwupd will never try put a large enough file to update
firmware of some device?
Firmware updates are exceptional and critical operations. They should
not be left to unattended daemons. The system configuration should not
be tailored for them.
The daemon may just notify the user. However it is still necessary to
save firmware files on user request to apply updates during next boot.
I consider 500 MB ESP as a kind of safety margin. Usually it is not
prohibitively expensive.
My experience is that laptop firmware updater,
launched from a USB stick, creates some files on the internal drive. Are you
I find hard to believe that it would be necessary. It would mean an
impossibility to update the firmware if the internal drive is dead or
not detected. Most likely there was a more straightforward solution to
update the firmware. If not, please share the brand of the computer so
that I can avoid buying one in the future.
I have not tried firmware update with failed internal drive, so I have
not idea if it will be started at all and if the USB drive will be used
as a fallback. Unless drive failure is caused by buggy firmware, I find
it safe to run firmware update when other components work properly.
It is HP ProBook. The vendor is not friendly to Linux despite the laptop
arrived with some ancient Debian installed ... to run FreeDOS inside Qemu.
sure that unified kernel images will not become default before the user
replaces their drive?
Are you sure that UEFI will not be replaced by something even more
bizarrely inexplicable before that happens?
I am unaware of UEFI replacement, however I have seen some news on UKI
in Fedora perhaps a couple of years ago.
Everybody is free to make their own conscious decision, but by default a
safe value should be suggested.
