Hello, Thaank you for all the replies so far.
On 2025-03-05 10:15, Michael Banck wrote:
Presumably because it will be written directly to their terminal.
Yes, this is one of the reasons. During a dist-upgrade you receive the changes, but it's many, many pages long and spotting the entry that renders your system dead is not easy.
I am not asking to create multiple ATTENTION banners at the end. All issues can be fixed as long as I can connect to the machine. Thus anything that would prevent the machine from booting (e.g. if it's known that the machine would not boot unless a grub-install is done) or having a functioning network connection, should be mentioned explicitly at the end.
The subject specifically points out an improvement for headless server upgrades. Chances are that these "special" notifications only happen now and then.
But it would certainly make the upgrade experience better. Cheers, K. C.P.S.: I admit that reading NEWS/UPGRADE files and articles is also important and that doing test migrations is best practices. On the other hand, it's not always possible to have a test bed for every single setup.
-- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
OpenPGP_signature.asc
Description: OpenPGP digital signature
