You are not logged in.
Hi!
I upgraded to systemd 221 few mins ago, and i noticed (after a reboot) that systemd-boot is still 220.
After a manual "bootctl update", and a reboot, now i'm on 221.
Shouldn't systemd.install provide a systemd-boot update function?
Thanks for your time!
Last edited by nierro (2015-07-01 08:06:01)
Offline
Letting the user handle bootmanager updates manually has been the sane default (!Ubuntu and !Grub for that matter) as long as I remember. I don't want my ESP to be touched unless I say so. It is also not in the capacity of bootctl to determin, whether it is installed, so that post install hook would need to do that. Given the dynamic nature of ESP mount locations, any automatic ESP handling will lead straight down to admin hell.
Online
This has been solved in a bug report, where i've been explained why it is not a good idea. I forgot to mark this as solved...sorry.
Thanks for your response too!
Offline
You could link that bug? I want read it be myself
Well, I suppose that this is somekind of signature, no?
Offline
Offline