Re: Automatic creation of last-known-good boot configuration

2024-07-10 Thread songbird
Dan Ritter wrote: > Jens Schmidt wrote: >> On Debian testing I've been bitten by the systemd upgrade and the >> systemd package split recently, rendering my dracut-LUKS-based >> system unbootable. I know that my warranty is void since I'm on >> testing, but both these issues would have been much

Re: Automatic creation of last-known-good boot configuration

2024-07-10 Thread Nicolas George
Jens Schmidt (12024-07-10): > On Debian testing I've been bitten by the systemd upgrade and the > systemd package split recently, rendering my dracut-LUKS-based > system unbootable. I know that my warranty is void since I'm on > testing, but both these issues would have been much easier to cope >

Re: Automatic creation of last-known-good boot configuration

2024-07-10 Thread Dan Ritter
Jens Schmidt wrote: > On Debian testing I've been bitten by the systemd upgrade and the > systemd package split recently, rendering my dracut-LUKS-based > system unbootable. I know that my warranty is void since I'm on > testing, but both these issues would have been much easier to cope > with if

Re: Automatic creation of last-known-good boot configuration

2024-07-10 Thread Michel Verdier
On 2024-07-10, Jens Schmidt wrote: > So I thought that there might be some automatism like this: > > If the currently used kernel and initramfs have been in use > already N times and if the boot time has been lower then M > minutes each time (and if some other conditions are fulfilled), >

Automatic creation of last-known-good boot configuration

2024-07-10 Thread Jens Schmidt
On Debian testing I've been bitten by the systemd upgrade and the systemd package split recently, rendering my dracut-LUKS-based system unbootable. I know that my warranty is void since I'm on testing, but both these issues would have been much easier to cope with if there had been some good backu