Dear maintainer,
I wonder if this fix can be backported to stable-pu and oldstable-pu,
since this bug may lead to data corruption. A possible approach might
be to mask the kexec init script in the systemd side, i.e. via
`systemctl mask kexec.service`, so that systemd users can get rid of
the kexec
On 1/11/23 15:40, Michael Biebl wrote:
Control: reassign -1 kexec-tools
Am 10.01.23 um 20:34 schrieb KOLANICH:
Package: systemd
Version: 252.4-1
Severity: grave
So do kexec-tools if a user has chosen to use it for
reboots during package configuration.
Either of the following can cause fs corrup
Processing control commands:
> reassign -1 kexec-tools
Bug #1028416 [systemd] systemctl kexec doesn't shutdown system properly and
corrupts mounted filesystems
Bug reassigned from package 'systemd' to 'kexec-tools'.
No longer marked as found in versions systemd/252.4-1.
Ignoring request to alter
Control: reassign -1 kexec-tools
Am 10.01.23 um 20:34 schrieb KOLANICH:
Package: systemd
Version: 252.4-1
Severity: grave
So do kexec-tools if a user has chosen to use it for
reboots during package configuration.
Either of the following can cause fs corruption (to the point one has to
use `fsck
Package: systemd
Version: 252.4-1
Severity: grave
So do kexec-tools if a user has chosen to use it for
reboots during package configuration.
Either of the following can cause fs corruption (to the point one has to use
`fsck -y`):
a) the procedure described in https://wiki.archlinux.org/title/Ke
5 matches
Mail list logo